| Author |
Message
|
| manishpnp |
 Posted: Tue May 24, 2011 6:47 am Post subject: performance problem in MQ 7.0 |
 |
|
Apprentice
Joined: 21 Feb 2008
Posts: 46
|
Hello,
Java-JMS based application communicating to Queue Manager(QMET) version WebSphere MQ 6.0.2.5 in AIX 5.3.
Application is put the message in request queue and get the message from response queue. This process is sucessfully completed within 1 seconds.
Total Time to Put the message in queue 60 msec
Total Time to Get the message in queue 80 msec
Question :-
Now We setup the new queue manager(QMET) version WebSphere MQ 7.0.1.4 in AIX 5.3 in different LPAR.
The same Java-JMS Application is pointing, communicating to new queue manager(QMET) WMQ 7.0.1.4 environment.
Application is put the message in request queue and get the message from response queue.
We done the analysis and found that :-
Put the message in request queue (this process sucessfully completed less than seconds as expected in previous m6.0 version)
Problem :-
While receiving(get) message from response queue it is taking long time in MQ 7.0 environment (approx 5 seconds).
Total Time to Put the message in queue 60 msec
Total Time to Get the message in queue 5097 msec
Note :-
1) We check and confirmed with network team and no issue.
2) We check and confirmed the sender/receiver/svrconn channel and everything is working fine.
3) There is no changes in application code (using same code which sucessfully response in MQ 6.0 environment.)
Need your help in below points :-
How to compare the configuration parameters between MQ6.0(QMET) and MQ7.0(QMET). How to find if any configuration/performance parameters missing in MQ7.0.
No changes in application code and only difference is mq version then why receiving message is taking much time!
What are the possible options to find the cause for this issue (any trace need to be enable at MQ/channel level?)
Any thread is getting timeout?
Thanks in advance for your responses.
manishpnp |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue May 24, 2011 7:17 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Don't double post! 
If you think this is in the wrong place, ask for it to be moved.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Tue May 24, 2011 9:06 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
does the message arrive on the queue and then the mqget takes 5 seconds (so its just the mqget) or is it the total time between mqput and mqget including all transfer times and application processing time? if the second one, it is maybe not related to the mqget .... make sure the message is in the queue, and then measure the mqget time. maybe mq statistics can help (max age ?!?)
_________________
Regards, Butcher |
|
| Back to top |
|
|
| skoobee |
| Posted: Tue May 24, 2011 10:41 pm Post subject: |
|
|
Acolyte
Joined: 26 Nov 2010
Posts: 52
|
[quote]We check and confirmed with network team and no issue[/quote]
They always say that!
See numerous previous posts here; they probably did a ping (12 chars) and it seemed to work quite quickly, and that is what they mean. |
|
| Back to top |
|
|
| manishpnp |
| Posted: Wed May 25, 2011 6:24 am Post subject: Re : performance problem in MQ 7.0 |
|
|
Apprentice
Joined: 21 Feb 2008
Posts: 46
|
Mr Butcher
I confirmed that all the messages are process and arrived on response queues within a second as expected behaviour in MQ 6.0 so there is no problem till message arrived in response queue.
Total time 1 seconds - between put the message/processes and arrived in response queue. (Everything is fine till here).
Only problem is MQGET while pickup the messages from response queue. It is taking 5-6 seconds.
Need your help to debug this issue!
Thanks,
does the message arrive on the queue and then the mqget takes 5 seconds (so its just the mqget) or is it the total time between mqput and mqget including all transfer times and application processing time? if the second one, it is maybe not related to the mqget .... make sure the message is in the queue, and then measure the mqget time. maybe mq statistics can help (max age ?!?) |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed May 25, 2011 9:11 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Have you applied the latest fix pack 7.0.1.5?
There are still a number of fixes in the JMS space there.
You may still need to open a PMR with IBM.
At the same time if you are using a client connection verify that the channel is set to only 1 concurrent conversation and not the default 10.
5 to 6 seconds sounds strangely close to the polling frequency of an MDB...
Have you looked into the effects of reducing this?
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| gouda |
| Posted: Fri May 27, 2011 4:45 am Post subject: |
|
|
Apprentice
Joined: 20 May 2001
Posts: 32
Location: Germany, Nuremburg
|
Hi manishpnp,
what about your mq jar files you are using ?
They are still v6, aren't they ?
It can be found in META-INF/manifest.mf
Wouldn't it be worth to replace them with those shipped by MQ V7 ?
_________________
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots.
So far, the Universe is winning.
https://en.wikiquote.org/wiki/Rick_Cook |
|
| Back to top |
|
|
|
|
