|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Wait interval at MQGET with CORRELID |
« View previous topic :: View next topic » |
Author |
Message
|
erhanpasa |
Posted: Mon Aug 08, 2011 11:29 pm Post subject: Wait interval at MQGET with CORRELID |
|
|
Newbie
Joined: 08 Aug 2011 Posts: 2
|
Hi,
At our environment we have z/OS V1.11, WebSphere MQ for z/OS V7.0.1. We got a new CICS application which is doing MQGET with CORRELID. But although we are using MQGMO-WAITINTERVAL (this is set as 5000 miliseconds) and MQGMO-WAIT options at this MQGET; sometimes we see that the program is waiting more than 5 seconds at MQGET call. It goes up to 20-30 seconds. This means that MQGMO-WAITINTERVAL option is not in affect. Can you please help us with this issue. How can we limit the wait time for MQGET call with CORRELID.
Regards,
Erhan |
|
Back to top |
|
 |
Mr Butcher |
Posted: Tue Aug 09, 2011 1:46 am Post subject: |
|
|
 Padawan
Joined: 23 May 2005 Posts: 1716
|
i recommend to double check the application program logic and to verify if your findings are correct.
If you are sure your program is fine, search the IBM site for known problems, then open a PMR. _________________ Regards, Butcher |
|
Back to top |
|
 |
Vitor |
Posted: Tue Aug 09, 2011 4:11 am Post subject: Re: Wait interval at MQGET with CORRELID |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
erhanpasa wrote: |
How can we limit the wait time for MQGET call with CORRELID. |
Using the code you've quoted on the face of it. I'd concur with my most worthy associate - check that the options which are in use are really in use.
If they are, does the application find the message in question after the 20-30 seconds or does it return a 2033? What is the depth of the queue where it's looking for the message?
What I'm wondering is what would happen if you issued a get for a specific correl id on a queue with a ridiculously large depth and/or no index on the correl id. If the scan of the queue took 20-30 seconds would the wait terminate after the wait interval or after the scan was finished?
Aside from all that, a PMR sounds like a logical move. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
zpat |
Posted: Tue Aug 09, 2011 4:33 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
Index the queue by Correlid. This will help performance if the depth has any significant value.
Also - when messages are only ever selectively retrieved - you need some way to remove the ones that (for whatever reason) are abandoned on the queue.
The best way is to create all the reply messages with an expiry value (even a long value like one day is fine). |
|
Back to top |
|
 |
erhanpasa |
Posted: Tue Aug 09, 2011 5:38 am Post subject: |
|
|
Newbie
Joined: 08 Aug 2011 Posts: 2
|
Hi,
The depth of the reply queue where we are looking for the message is very low since we are creating all the messages with expiry time. We get those response times during performance tests, and I am not sure what return code we get for those MQGETs that last 20-30 secs.
We will try to re-check the application logic and the options that are used.
Thanks,
Erhan |
|
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
|
|
|
|