Reputation: 22343
We are using Websphere MQ 7.5 with the Javax-JMS-classes and have some performance-problems, which aren't reproducable.
I have isolated the performance-issue to these two method-calls createSession
and send
.
These two calls sometimes take a large amount of time(> 300ms per message). Often there is a Object.wait
call which causes the slowdown. So maybe jms is waiting for resources.
Sometimes I can send 500 messages without any occurence of that issue, but suddenly it's really slow. It isn't possible that the problem is in our code, because every step before doesn't take much time. Only these two JMS method calls.
So my question is, what could be the cause for the sudden performance-drop?
Is it possible to debug it by using the queuemanager-logs?
Any idea is helpful.
Edit:
We are using client-bindings and the SHARECNV-setting is set to 10.
Upvotes: 1
Views: 3026
Reputation: 7456
I have isolated the performance-issue to these two method-calls createSession and send.
I hope you are NOT doing a createSession method call for each message put to the queue because if you are, that is a TERRIBLE design.
Do 1 createConnection method call and 1 createSession method call then send all of your messages. If you have multiple threads then use connection pooling.
Upvotes: 2