| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JMS AsynchReceiver hogging CPU? |
« View previous topic :: View next topic » |
| Author |
Message
|
| StefanSievert |
 Posted: Thu Mar 18, 2004 12:28 pm Post subject: JMS AsynchReceiver hogging CPU? |
 |
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
We see an interesting behavior on some of our servers. A JMS application running under WAS uses an asynchronous queue receiver to process replies. This causes a helper thread to be started, which sits on the queue with an MQGET, supposedly using a 5 second wait interval (default JMS polling interval). Works as designed, so far.
Once this thread gets started, the CPU utilization on some of the servers where the application runs, increases to 20-30%; a behavior that we don't see in another environment, which - I was made to believe - has the same software levels installed.
It is the JVM process that runs the application, that consumes the CPU. We haven't done a very detailed analysis yet, but I am curious if anybody has seen something similar when using asynch JMS receivers and what you have found the reason was.
Thanks,
Stefan
PS. In case it matters, the application uses CLIENT bindings to an off-box queue manager in the LAN
_________________
Stefan Sievert
IBM Certified * WebSphere MQ |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Thu Mar 18, 2004 12:58 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| I haven't seen this behavior. However, I'm using MDBs under WAS 5. You mentioned asynchronous queue receiver rather than MDB. Can I take this to mean that you are doing something with WAS 4? |
|
| Back to top |
|
|
| StefanSievert |
| Posted: Thu Mar 18, 2004 2:16 pm Post subject: |
|
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
| bower5932 wrote: |
| I haven't seen this behavior. However, I'm using MDBs under WAS 5. You mentioned asynchronous queue receiver rather than MDB. Can I take this to mean that you are doing something with WAS 4? |
I think that what the application group is running on. It is a request/reply application, so the MDB approach is not the first one we could think about, since they are planning on moving the transport onto web services soon.
But we are using an MDB on the server end of the picture and that works like a champ!
_________________
Stefan Sievert
IBM Certified * WebSphere MQ |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
