| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Performance Issue with MQ v7.5.0.1 |
« View previous topic :: View next topic » |
| Author |
Message
|
| ArchieOops |
 Posted: Tue Oct 08, 2013 8:23 am Post subject: Performance Issue with MQ v7.5.0.1 |
 |
|
Newbie
Joined: 18 Nov 2011
Posts: 6
|
Hi All,
Thanks in advance for your valuable advice.
We have a Java Application which use MQ Client connections to read/write messages to Queues on a Queue Manager running on a separate server.
We have a dedicated server connection channel which is being used for communicating to the QMngr from the application.
What I want to know is what is the maximum number of client connections a server connection channel can handle without performance degradation?
We are seeing a latency of upto 4-5secs in reading and writing messages to the Queues. This does not happen for all the messages but it happens for almost 30% of the messages.
Any help or suggestion is greatly appreciated. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Oct 08, 2013 8:35 am Post subject: Re: Performance Issue with MQ v7.5.0.1 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ArchieOops wrote: |
| What I want to know is what is the maximum number of client connections a server connection channel can handle without performance degradation? |
Depends entirely on the server resources available to the queue manager, but hundreds if not thousands. If you're not actually getting errors, then this implies that you've not hit the artificially impossed maximum connections limit designed to stop channel flooding. Extrapolating further, you either have the limit (which is user configurable) set ridiculously high or (more likely) you have not got enough connections to reach this number and hence have so few connections degradation is unlikely.
| ArchieOops wrote: |
| We are seeing a latency of upto 4-5secs in reading and writing messages to the Queues. This does not happen for all the messages but it happens for almost 30% of the messages. |
I'd look first into whatever's running your Java & if it has a connection pool that needs tuning. Next I'd look at your code and see under what circumstances it connects or reconnects to the queue manager, and if some bug causes it to do this 30% of the time. Next I'd identify at exactly what point this latency occurs; is it actually 4-5 seconds while the application waits for the queue manager to respond, is it 4-5 seconds while the queue manager waits for disc I/O, what?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Oct 08, 2013 2:34 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And finally I'd look at channel behavior and expected bottle necks on sockets.
Think share conversation and it might not be something you'd want to take advantage of in your case.... or the default value of 10 is too high for you... YMMV! 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ArchieOops |
| Posted: Tue Oct 15, 2013 8:47 am Post subject: |
|
|
Newbie
Joined: 18 Nov 2011
Posts: 6
|
Thanks for your replies. We did look at things based on your suggestion but nothing seems to help.
We have finally engaged IBM and their Level 3 is working with us now. On a high level it seems to be some issue with handle leaks on the MQ Server.
We are running MQv7.5.0.1 on Windows 2008 R2 server.
Have you guys heard or seen any similar issues? |
|
| 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
|
|
|
|
