| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Temporary reply queue combined with Remote qmgr |
« View previous topic :: View next topic » |
| Author |
Message
|
| garasan |
 Posted: Thu May 24, 2018 3:51 am Post subject: Temporary reply queue combined with Remote qmgr |
 |
|
Apprentice
Joined: 22 Jul 2008
Posts: 42
Location: Antwerp, Belgium
|
Hi,
a little call for help since I'm out off idea's
Situation:
2 qmgrs, I will call them A & B, with working sender en receiver channels in between (2 ways). This has been tested and verified.
Note: The TRANSQ names match the receiving QMGR name on the other end, and this on both sides.
App A is running on WAS6.5
App B is running on WAS8.5.5
QMGR A version is v8
QMGR B version is V7.1
App A sends a message to a remote queue on qmgr A. This with the creation of a local temporary reply queue on qmgr A. (Verified and the queue is there at the time of the sending off the message)
This remote queue points to a local queue on qmgr B.
The message does arrive on the local queue in qmgr B and is picked up by App B, who replies.
And this is where the problem lies. The reply message ends up on the SDLQ
Looking at the message on the SDLQ, it has no DLQ header.
But the ReplyToQMgr is correct and matching the name of the existing Transmit queue.
The ReplyToQ is also correct and matching the created temporary reply queue name...
The Temp Reply queue disapears after 30s and at the same time App A fails with 'Timeout while waiting for message on reply queue'
The while process should take at most 5s. (Shouldn't even be 1s, but I'm taking a marging)
Permissions should all be good.
Any hint is welcome...
_________________
Regards |
|
| Back to top |
|
 |
| garasan |
| Posted: Thu May 24, 2018 4:05 am Post subject: |
|
|
Apprentice
Joined: 22 Jul 2008
Posts: 42
Location: Antwerp, Belgium
|
The Way I get is this: (Simplified so I'm as clear as possible)
1. App A sends message to remote queue with added request to open a TempRQ to Qmgr A.
2. Qmgr A sends the message to Qmgr B since sent to a RQueue and Creates a TEMPRQ
3. Message arives on qmgr B.
4. App B reads the message with the reply info from the initial message.
5. App B processes the message and sends a reply to the TransQ from Qmgr A with info from step 4 to qmgr B.
6. Qmgr B is not able to find the TempRQ on Qmgr A and fails..
I'm basing this on below article..
https://www.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.con.doc/q015410_.htm
Since all queue's in step 6 are present, I'm starting to doubt step 5.
_________________
Regards |
|
| Back to top |
|
|
| exerk |
| Posted: Thu May 24, 2018 4:38 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Check that App B is committing the message before the Temp Dyn queue time-out set.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| garasan |
| Posted: Thu May 24, 2018 4:41 am Post subject: |
|
|
Apprentice
Joined: 22 Jul 2008
Posts: 42
Location: Antwerp, Belgium
|
OK, thanks for the tip..
Going to verify that...
_________________
Regards |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu May 24, 2018 4:37 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| Quote: |
| Looking at the message on the SDLQ, it has no DLQ header. |
That seems a bit unusual. Are there any message delivery errors on both qmgr's error logs?
_________________
Glenn |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu May 24, 2018 5:16 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
My guess is the message on the DLQ is not the reply, but the request.
The app on B picks up the request, fails, tries to back it out to a backout queue, can't so puts it to the DLQ. That explains why no DLH, and why the messages has a Reply To Q and the Reply to QM for A. Note that if this was the reply message produced on B, the reply to QM would be B, and the Reply To Q would be blank.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| garasan |
| Posted: Fri May 25, 2018 1:00 am Post subject: |
|
|
Apprentice
Joined: 22 Jul 2008
Posts: 42
Location: Antwerp, Belgium
|
Hi All,
after more investigation I had to conclude it was related to an application (B) problem, rather than an MQ problem...
The Train of my thoughts was indeed correct. (Damn, that feels good :-))
I came to that conclusion because of below 3 reasons:
1. The message at the SDLQ was missing a DLQ header, wat made me assume it was not MQ putting it there, since MQ would add a DLQ Header. So it's almost sure it is done by the application itself. (Idealy it would add a DLQ header too, but that is a different discussion.
2. I tripple checked everything on the MQ level and wasn't able to find anything wrong.
No errors in the error log , all permissions where there, etc....
3. The application (B) log showed an error at the time of reply.. Offcourse the DEV's took the quick road and initialy blamed it on MQ.
Thanks for all the tips on this.. It did help to confirm my train of thoughts and build up a solid cause to defer the problem from the MQ level to an application level.
_________________
Regards |
|
| 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
|
|
|
|
