| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How to capture time taken by MQ to handle request-reply msg |
« View previous topic :: View next topic » |
| Author |
Message
|
| MQMB&WAS |
 Posted: Tue Sep 19, 2017 7:20 am Post subject: How to capture time taken by MQ to handle request-reply msg |
 |
|
Centurion
Joined: 12 Jun 2016
Posts: 130
|
Hello,
I need to capture the total time MQ takes to handle a request-reply message (excluding the time taken by the apps to process the msg). Could someone suggest any ways/tools? Thanks. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Sep 19, 2017 7:46 am Post subject: Re: How to capture time taken by MQ to handle request-reply |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| MQMB&WAS wrote: |
Hello,
I need to capture the total time MQ takes to handle a request-reply message (excluding the time taken by the apps to process the msg). Could someone suggest any ways/tools? Thanks. |
Enable the statistics and process them
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Sep 19, 2017 9:02 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Let's see...
On the client platform
- capture the time/date when the client app MQPUTs the request message
- capture the time/date when the client app MQGETs the reply message
- this encompasses total time, including server app processing
On the server platform (where server app runs), you will need to
- capture time/date when server app MQGETs the request message
- capture time/date when server app MQPUTs the reply message
- this encompasses server app processing
Subtract the server app processing time from total time, and Voila!
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Tue Sep 19, 2017 5:11 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| Quote: |
| Subtract the server app processing time from total time, and Voila! |
Correct. This requires timings captured from both platforms that can be correlated by individual transactions. With MQ processing, this really needs to be better than 1 millisecond resolution to get meaningful results. If the client and qmgrs are on different servers, competing network traffic could heavily skew the results.
_________________
Glenn |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Sep 19, 2017 11:17 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Use support pac IH03 - there are tools in there (other than RFHUTIL) which can be used to drive the application and produce an average response time using a decent sample of messages (which can have varying payloads).
You don't need millisecond precision tools if you test with thousands of messages and calculate the average.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| 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
|
|
|
|
