Information on changes to the WebSphere MQ JMSReplyTo header field
Preventive Service Planning
This document outlines some recent changes that have occurred with respect to the WebSphere MQ JMSReplyTo header field.
WebSphere MQ Version 184.108.40.206 and 220.127.116.11 changed the way the JMSReplyTo field on received messages was constructed, to make the behavior of JMS applications consistent with other WebSphere MQ clients.
As a result of customer feedback, the default behavior of WebSphere MQ Version 18.104.22.168 (and later) has reverted back to the pre-22.214.171.124 behavior, where the contents of the JMSReplyTo header field is based on the value in the message's RFH2 header, which is equivalent to the value set by the sending application. If you want to have the JMSReplyTo header populated based on the contents of the message's MQMD ReplyToQueue and ReplyToQueueManager header fields, then you have two options:
- Set the new Queue Destination property REPLYTOSTYLE to MQMD using JMSAdmin.
- Pass in the following Java Virtual Machine system argument to the application:
Full details can be found in APAR IZ36978.
For the WebSphere MQ Version 126.96.36.199 and 188.8.131.52 JMS client, the default behavior is to construct the JMSReplyTo from the ReplyToQueue and ReplyToQueueManager fields from the message's MQMD, which is different behavior to that of Version 6. WebSphere MQ Version 184.108.40.206 (and later) maintains this default behavior, but allows it to be reverted to the Version 6 style by setting either the REPLYTOSTYLE property or the system argument com.ibm.mq.jms.replyToStyle to RFH2.
WMQ MQ MQSeries
More support for:
Software version: 220.127.116.11, 18.104.22.168, 22.214.171.124, 7.0, 126.96.36.199
Operating system(s): AIX, HP-UX, IBM i, Linux, Solaris, Windows, z/OS
Reference #: 1383887
Modified date: 19 July 2013
Translate this page: