I have a JMS client sending a message to an Websphere MQ queue, and expecting a reply. My client is using the JMS API to send a request message, the client reading the request will be a program using the Websphere MQ API (not JMS).
My understanding, is that the JMS Message ID I send in the message gets converted to a byte array when the consumer picks up that message in the MQMD (mq message descriptor) MessageId field.
I've configured the application server (WAS) where my request queue is defined as MQ, so the message on the queue doesn't appear to have the RFH headers in the message body when the consumer picks it up.
My trouble is on the reply side, where the MQ client is sending back a reply to my JMS application. What should my filter be when I create the MessageConsumer?
My JMS client needs to look for the specific correllid in the incoming message, but I'm a little confused because the MQ side doesn't put anything in the JMS header, but is setting the MQMD CorrellId, not the JMS CorrellId value.
What JMS CorrellId should I be looking for? When I send my message it's a simple String, but when the MQ client gets the message, the output on my client shows that the messageId from the reply is a byte array.
Any help appreciated!
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: JMS client request/reply from WebSphere MQ Queue