| Author |
Message
|
| oli |
 Posted: Wed Oct 10, 2012 3:16 am Post subject: ReplyTo in MQMD vs. Rto in RFH2 |
 |
|
Acolyte
Joined: 14 Jul 2006
Posts: 68
Location: Germany
|
Hi all,
we have a very strange behavior in two different environments regarding the reply-to destination when using JMS.
We put a message into a queue with an MQMD and an RFH2 header. The reply-to information in MQMD and RFH2 is different (don't ask why), e.g.
In MQMD we have:
| Code: |
ReplyToQMgr=QMGR1
ReplyToQ=QUEUE1
|
In RFH2 we have:
| Code: |
<jms>
...
<Rto>queue://QMGR2/QUEUE2</Rto>
....
</jms>
|
An MDB in Websphere Application Server (V6.1) gets the message from the queue an uses method
to determine the reply-to destination.
The curious thing now is that on one environment the above mentioned method returns
| Code: |
| queue://QMGR2/QUEUE2 |
whereas on the other environment the method returns
| Code: |
| queue://QMGR1/QUEUE1 |
So in one case the reply-to information from the MQMD is used an in the other case from the RFH2 Header.
Any ideas what may lead to that behavior???
Thanks, Oli |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Oct 10, 2012 3:26 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I'd start by looking for differences between the rest of the MQMD and the rest of the RFH2 header.
Even something as basic as one is a text message and one is a bytes message might change this.
Then I'd look at the code that writes the messages, and confirm that it's the same code in both cases.
Then I'd look at the versions of the queue managers involved and the versions of the MQ libraries involved. |
|
| Back to top |
|
|
| oli |
| Posted: Wed Oct 10, 2012 3:32 am Post subject: |
|
|
Acolyte
Joined: 14 Jul 2006
Posts: 68
Location: Germany
|
| We checked almost everything except the libraries. At the moment we are checking the library versions. At the moment I assume that the JMS implementation is different ... |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Oct 10, 2012 3:33 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
edit: sorry, lost track a second. coffee not kicking in yet...
So you send the exact same message in both environments and observe separate behavior?
And MQ is at the exact same version in both environments, at least the queue managers...
And the MDB hosting environment is at the exact same version? And the configuration of the QCF and mdb listeners and etc. is all the same? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Oct 10, 2012 2:02 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I would look at the difference in the destination definition
For one definition the destination is set up as JMS and you get
queue://QM2/Queue2
On the other the destination is set up as MQ and you get
queue://QM1/Queue1
Identical code. Different JNDI
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
