WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Resolving problems when using publish/subscribe
Use the advice given here to help you to resolve common problems that can occur when you run publish/subscribe applications.
Application responses are not received
Your application is not receiving publications
Publishing a message causes a filter error
- Scenario: When you publish a message, you receive an error response message with reason text MQRCCF_FILTER_ERROR.
- Explanation: A broker returns this message to a publication when subscriptions have been registered that specify filter expressions (for Content Based Routing) and an error has been encountered when the broker attempts to filter the published message. This situation can occur, for example, if a message is published that includes unsupported data types, or if the message body is corrupted.
Symbols in subscription filters cause problems
The Publication node fails with MQRC 2035
- Scenario: The Publication node fails with MQRC 2035.
- Explanation: WebSphere Message Broker publishes messages with the user ID in the original message, not the broker service ID.
- Solution: You can force WebSphere Message Broker to use the broker service ID in all circumstances by setting the environment variable MQSI_PUBSUB_USE_BROKER_USERID to any value. If there is no MQMD header, or if there is an MQMD header but its UserIdentifier field is blank, WebSphere Message Broker continues to use the broker's user ID.