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 that occur when connecting the WebSphere Message Broker Toolkit and a broker
Use the advice given here to help you to resolve common problems that can arise when you connect to a broker.
Your broker is not recognized by the WebSphere Message Broker Toolkit
- Scenario: Your broker is not recognized by the WebSphere® Message Broker Toolkit.
- Explanation: Broker names in the workbench are case sensitive.
- Solution: When you identify a broker in the WebSphere Message Broker Toolkit, make sure that you use the same case that was used when it was created. On some operating systems, the name of the broker might be folded to uppercase when it was created, even though you entered its name in lowercase.
You cannot connect to the broker from the WebSphere Message Broker Toolkit or command line
You cannot connect to a migrated broker
- Scenario: You cannot connect from the WebSphere Message Broker Toolkit, the WebSphere Message Broker Toolkit, or a WebSphere Message Broker Toolkit application to a broker that you have migrated to Version 8.0.
- Explanation: The connection is failing because the WebSphere MQ channel does not exist. When you migrate a broker to Version 8.0, the default server connection channel SYSTEM.BKR.CONFIG is created if it does not exist. However, if the broker shared a queue manager with a Configuration Manager, this channel is deleted when you delete the Configuration Manager.
- Solution: Re-create the server connection channel SYSTEM.BKR.CONFIG on the queue manager.