Problem receiving message through Messaging Bridge

Question

          Hi!
          I am using WLS7.0, and trying to correctly setup two messaging
          bridges: one from a WLJMS_SEND_QUEUE to a MQJMS_SEND_QUEUE and
          one from a MQJMS_RECEIVE_QUEUE to a WLJMS_RECEIVE_QUEUE.
          When sending on the local send queue WLJMS_SEND_QUEUE, the
          messages are being forwarded to the remote send queue
          MQJMS_SEND_QUEUE as expected, but when setting the JMSReplyTo
          field to the local receive queue WLJMS_RECEIVE_QUEUE, no
          message is received.
          Do I really need to set the JMSReplyTo field to the remote
          receive queue? I would like to work only with the local
          queue definitions... if possible.
          Any hint would be greatly appreciated,
          Guillaume Bedard
          

Answer 1

This is a dark section of the JMS specification. From section 3.12,
          "Note the following exception case when a provider is handling a foreign
          message implementation. If the foreign message implementation contains a
          JMSReplyTo header field that is set to a foreign destination implementation,
          the provider is not required to handle or preserve the value of this header
          field."
          This is to allow wiggle room with respect to serialization and validation of
          foreign destinations. In your scenario you have a WebLogic sender that
          wants a reply on a WebLogic queue. You put a replyTo of the WebLogic queue
          in the message. When that message makes it to MQSeries land and it tries
          to respond using an MQSeries producer to a WebLogic queue, bad things
          happen. There is no way it can work because MQSeries has no way to handle
          WebLogic destinations. In reality the MQSeries application receiving the
          message does not want to send it to the WebLogic queue, but to the MQSeries
          queue that forwards to the WebLogic queue. That means the WebLogic producer
          sends to a WebLogic queue, but puts a replyTo of an MQSeries queue (of
          which it knows nothing about in this scenario), and then receives on the
          WebLogic queue (even though it said to reply to the MQSeries queue).
          Then of course there is the serialization of the foreign destination. You
          could just serialize to bytes, and leave it that way. WebLogic does
          validation of replyTo queues and the like, so it would try to unserialize
          the replyTo destination specified in the message. If this is an MQSeries
          destination, then WebLogic may not have the necessary classes on the server
          to unserialize the replyTo destination.
          _sjz.