| Author |
Message
|
| MQnode |
 Posted: Wed Jun 26, 2013 8:07 am Post subject: MQ Reply Message Performance |
 |
|
Newbie
Joined: 26 Jun 2013
Posts: 3
|
| We are running some tests on and Iseries replying to a message where the return message size is 5mb and the reply is taking 15 minutes to reach the webservice requester. Is this normal? |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Wed Jun 26, 2013 8:55 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 26, 2013 8:57 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| MQnode |
| Posted: Wed Jun 26, 2013 9:15 am Post subject: |
|
|
Newbie
Joined: 26 Jun 2013
Posts: 3
|
| Quote: |
| how do you know the message is taking 15 minutes to reach the requester. |
I watch this process in debug. I can see where the trigger program finishes processing and executes the reply. I have a front end to test the web-service.
Thank you for the links. |
|
| Back to top |
|
|
| hughson |
| Posted: Thu Jun 27, 2013 12:57 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
If you are watching this all happen, then I assume you can see where the message spends its time. How long does it spend on queues, such as transmission queues, or other queues - a reply queue perhaps - before it is picked up by each party in the return flow.
Perhaps you can furnish us with the various parts of the return flow, with queues, channels etc, and the portion of the 15 minutes spent in each part as you see it though your debug view, and then we can comment more appropriately to help you out.
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Jun 27, 2013 3:31 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
Can you code a debug point in the requester app to display the time it consumed the reply message and the PutTime from the reply message? This will isolate the issue to MQ or the back end app.
_________________
Glenn |
|
| Back to top |
|
|
| MQnode |
| Posted: Fri Jun 28, 2013 10:30 am Post subject: |
|
|
Newbie
Joined: 26 Jun 2013
Posts: 3
|
Here are my stats from a batch run test. This is request/reply.
10:46:36 processing started - trigger fired
10:49:49 processing complete
10:49:51 Reply message sent
11:02:30 Message appears in web-service
For the identical run, From the Web-service log. Keep in mind our puters are off a tad.
ActionName : SearchCaseDataHL7:request
ActionDate : 6/28/2013 10:49:58 AM
Message :
| Code: |
MSH|^~\&|CCS||COMPWORKS||20130619090414||QRY^A19||D|2.3|
ZCR|E|FL^24030~FL^30184~TX^6247~TX^3430~TX^3434~FL^30187~F
L^32576~FL^19361~TX^3452~CA^127245~TX^3437~FL^532~FL^2089
0~CA^131550~NC^4006~NC^2754~CA^33329~FL^180~TX^3464~CA^
170914~IN^3221~CA^43320~CA^43412~CA^131187~CA^13529~FL^1
1392~CA^206459~CA^138014~CA^170910~CA^12925~CA^29659~CA
^118943~CA^57792~CA^81947~CA^175997~TX^3442~CA^67107~CA
^172925~CA^155761~CA^43516~CA^27938~CA^57793~CA^67108~FL
^183~CA^165373~NJ^13971~WA^17304~CA^18899~CA^18896~CA^7
0504~CA^67114~CA^15754~CA^15934~CA^99566~TX^3441~CA^149
161~NJ^3842~CA^42243~CA^57794~IN^3508~TX^2413~CA^75730~C
A^170730~WA^7982~CA^84388~CA^158993~CA^149400~CA^172926
~FL^184~TX^3903~CA^205965~CA^209797~WA^7989~NJ^10466~CA
^135924~TX^3796~CA^205556~FL^27435~TX^6235~CA^160446~CA^
165673~CA^209254~CA^118964~WA^20551~CA^150557~TX^541~FL^
19069~NJ^10249~FL^21151~CA^121157~FL^11872~CA^162655~CA^1
65188~CA^107569~CA^176279~CA^123827~CA^204536~CA^205568~
CA^209789~CA^170911~FL^29694~CA^172548~CA^210248~CA^2051
63~FL^29503~CA^202179|20070520|20130619|I||||N|
|
UserName : Jeff
IPAddress : 10.8.253.77
------------------------------------------------------------------------------
ActionName : SearchCaseDataHL7:reply
ActionDate : 6/28/2013 11:05:31 AM |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Jun 30, 2013 5:07 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| MQnode wrote: |
Here are my stats from a batch run test. This is request/reply.
10:46:36 processing started - trigger fired
10:49:49 processing complete
10:49:51 Reply message sent
11:02:30 Message appears in web-service
ActionDate : 6/28/2013 10:49:58 AM
Message :
| Code: |
| MSH|^~\&|CCS||COMPWORKS||20130619090414||QRY^A19||D|2..... |
UserName : Jeff
IPAddress : 10.8.253.77
------------------------------------------------------------------------------
ActionName : SearchCaseDataHL7:reply
ActionDate : 6/28/2013 11:05:31 AM |
OK so let's be very specific.
You say 10:49:51 message sent but I did not see any indication that the message was committed? If the app takes a few minutes to before commit this will influence greatly the overall response time.
Same difference, you do not distinguish between message available and message read. With large messages this can mean quite some time, especially if the network is not of the top best quality kind.
So there is no telling if the 15 minutes is due to reading the message on a bad network, or time difference between machines, or time difference between put and commit....
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
