| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| How to configure 2 apps/services with a common queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| fjb_saper |
 Posted: Thu Sep 16, 2010 1:17 pm Post subject: |
 |
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The reasonable thing is to change the sending applications to expect the response not with the messageId but with the correlation Id.
On the input queue you have an MDB that processes every message. Depending on correlationID it chooses the new destination and moves the message id to the correlationId before sending.
Your server process (MDB) uses the correlationID as passthrough to the reply message.
Each application has its own input queue. However for the sake of the requesters you still have only one destination...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
 |
| weskelton |
| Posted: Thu Sep 16, 2010 2:18 pm Post subject: |
|
|
Novice
Joined: 22 Feb 2010
Posts: 10
|
| Quote: |
| The reasonable thing is to change the sending applications to expect the response not with the messageId but with the correlation Id. |
That may be the reasonable thing to do, but at this point, it's not really an option. This becomes a viable option at the point these clients are replaced. Of course, at that point, everything becomes fair game. For now, we can assume that the clients will not be changing. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Sep 16, 2010 4:09 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
So getting back to the issue at hand, there should be some indication in a log or etc. as to exactly why the second listener is not actually listening.
Or at least not actually reading messages.
There may be messages in your MDB container's log, there may be errors in the MQ error logs for the qmgr.
If you're using MQ client connections - you haven't said, i think - then you can enable client tracing and see what's going on. You can also do this if you're using bindings connections but it's maybe a bit harder to weed out the right things.
You can add an error / exception listener to your session or connection or whatever it is, and see if you receive any calls to that. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
