Request messages going through wrong operation (multi operation AMX SOAP/JMS service) when service is using JMS provider WebSphere MQ.
Article ID: KB0088750
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix Service Grid | - |
| Not Applicable | - |
Description
Description:
This happens due to a MQ defect which is fixed in WebSphere MQ V7.0 Fix Pack 7.0.1.10. A WebSphere MQ v7 JMS client application using a selector is working properly when connected to a multi-instance queue manager. After the primary instance of the queue manager fails over to the secondary instance, the client reconnects but receives the wrong messages which do not match the selector.
A JMS Consumer was created with a message selector set (AMSG Services) which was correctly passed to the Queue Manager during the MQOPEN call. The multi-instance queue manager then falls over causing the WebSphere classes for JMS code to automatically reconnect to the secondary instance. The reconnect was successful but the application then received a message on this JMS Consumer that did not match the message selector that was originally set.
Symptoms:
Cause:
Resolution
Issue/Introduction
Additional Information
Feedback
