Explanation | The reason code was returned by an event broker. |
Action | Please refer to the WebSphere MQ Event Broker Programming Guide for an explanation of the reason code. For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided. |
Explanation | Only responses to register and deregister subscriptions and publication messages are expected from the event broker. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The reason code was returned by an event broker. |
Action | Please refer to the WebSphere MQ Event Broker Programming Guide for explanation of the reason code. For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Inbound and outbound profiles should specify the same topics. |
Action | Modify the mapping profiles to use same topics for both inbound and outbound profiles. |
Explanation | Only a single profile is registered for each topic in one direction to avoid duplicate messages. Messages will not be lost as a result of this removal. |
Action | Remove the duplicate mapping from the configuration. |
Explanation | Overlapping profiles are not registered to avoid duplicate messages. Messages will not be lost as a result of this removal. |
Action | Remove the overlapping profile from the configuration. |
Explanation | The only wildcard supported is # at the end of a topic. |
Action | Update the configuration to use valid topics. |
Explanation | The only wildcard supported is # at the end of a topic. |
Action | Update the configuration to use valid topics. |
Explanation | The attribute value has been ignored. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | All mandatory fields should be filled in for topic mappings. |
Action | Complete the topic mapping configuration. |
Explanation | Only responses to register and deregister subscriptions are expected from the event broker. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Only full responses containing request details of register and deregister subscriptions are expected from the event broker. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The correlation ID for responses to commands from event broker should match the correlation ID specified in the command. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | Topic spaces referenced by topic mappings should be created explicitly to create a mapping. |
Action | Create the missing topic space. |
Explanation | The broker input queue name is required to automatically route reply messages. This warning may be ignored if reply messages are not required. |
Action | The administrator must correctly fill in the broker input queue name in the named topic mapping. |
Explanation | If the message does not give sufficient information, check previous messages for further help. |
Action | See previous messages for further information. |