Troubleshooting
Problem
The desired behavior in a particular scenario is to have the response Message ID be the same as the request message. The appropriate configuration of "Response Message ID: Copy from the Request Message ID." is selected. However, the Message ID of the response message does not have the desired value, but a different, random value.
Cause
To be able to set the Message ID, the JMS destination queue needs to have the property 'MQMD WRITE ENABLE" set to ENABLED. This property allows a JMS application to set the value of the MQMD fields.
If the messaging resources on the server have been created manually, certain custom properties might not have been set correctly. This corresponds to using the Specify the JNDI for the pre-configured WebSphere MQ resources option.
Resolving The Problem
For all JMS queue resources that are created manually for use with an MQ binding, set the following custom properties:
For Send Destinations:
Custom Property Name: MDWRITE Value: YES
Custom Property Name: MSGBODY Value: MQ
Custom Property Name: MDMSGCTX Value: SET_ALL_CONTEXT
For Receive Destinations:
Custom Property Name: MDREAD Value: YES
Custom Property Name: MSGBODY Value: MQ
Custom Property Name: MDMSGCTX Value: SET_ALL_CONTEXT
If in doubt, set all properties on the destination and ignore the intended use of Send/Receive:
Custom Property Name: MDWRITE Value: YES
Custom Property Name: MDREAD Value: YES
Custom Property Name: MSGBODY Value: MQ
Custom Property Name: MDMSGCTX Value: SET_ALL_CONTEXT
You can also use the Specify the properties to use to configure WebSphere MQ Resources option to generate a sample set of MQ messaging resources. You can use these generated resources as a template to set the correct custom property values for resources created manually.
The Related URLs contain more information about these properties.
Related Information
Historical Number
68336
004
000
Was this topic helpful?
Document Information
More support for:
WebSphere Process Server
Software version:
7.0, 6.2, 6.1.2, 6.1
Operating system(s):
AIX, HP-UX, IBM i, Linux, Solaris, Windows, z/OS
Document number:
483851
Modified date:
15 June 2018
UID
swg21617122