| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How long did my MQGEt wait? |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Thu Aug 29, 2002 9:42 am Post subject: How long did my MQGEt wait? |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7716
|
My mainframe app sends a request and immediately goes to the reply queue to wait for the reply. We have the wait set to 500 milliseconds, which is a business requirement (hope) that this transaction comes back in that amount of time.
The request goes to MQSI to be converted from COBOL to XML, to a distributed platform to have the request processed, the XML reply then goes thru MQSI to be converted back to COBOL before the reply is placed to the reply queue back on the mainframe.
20% of the GETs are getting 2033, but we do see those replies back on the reply queue. I assume that 500 milliseconds is to little. Is there anyway to know what wait interval will satisfy 99.9% of the transactions other than bumping up the wait time a little every couple of days till it seems to work?
I would like to be able to jack the time up to say 5000 milliseconds and then run with it a week, at the end of which I would like to say to the customer "Hey, the average wait time was 453 milliseconds. 90% came back in 600 milliseconds. The shortest wait was...."
Is there any way/tool to do this?
As for those reply messages that seem to make it back to late, is there any way/tool to tell how long they took to make the round trip? (System clocks between all the machines are not synced.)
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| bduncan |
| Posted: Thu Aug 29, 2002 3:46 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
The clocks may not be synced between systems, but the reply message is coming back to the same machine that sent out the original request. In this case, you should be able to take a timestamp just before your MQPUT and actually place this somewhere within the request message. Right after your MQGET succeeds, take another timestamp and compare with the value in the message you just retrieved. This should give you the round-trip time. So, if you bump your wait time to a high enough value that you get 100% of the messages before they time out, do this for a week, and then look at the average roundtrip time (you'd probably want to calculate the standard deviation as well) you can make a good stab at a roundtrip time that will catch 50%, 90%, 99.9%, etc., of the messages...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| 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
|
|
|
|
