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

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

  • Scenario: Error messages are issued when you try to connect to the broker from the WebSphere Message Broker Toolkit or the command line.
  • Solution: The following table shows the checks to carry out when an error message is issued in the WebSphere Message Broker Toolkit, or returned to the command line, when you try to connect to the broker:
    Error message Actions
    WebSphere Message Broker Toolkit Command line
    BIP0914E BIP1046E with WebSphere MQ reason code 2059 Check that the broker queue manager and listener are running, and that the correct port is specified for the queue manager.

    (The WebSphere MQ documentation describes the WebSphere MQ return codes.)

    BIP0889E BIP1047E Check that the broker is running.

    Check the system event log to ensure that the broker is available for use, and correct all errors that are shown.

    BIP0915E BIP1046E with WebSphere MQ reason code 2035 Check that the WebSphere Message Broker Toolkit local user ID is created on the broker system. If it is not, create it.
    Check if the WebSphere Message Broker Toolkit local user ID that is created on the broker system is authorized to connect to the broker queue manager.
    • Use the WebSphere MQ dspmqaut command to determine what WebSphere MQ authorities the user has.
    • If necessary, add the WebSphere Message Broker Toolkit local user ID to the mqm group on the broker system.

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.

You cannot connect to a remote broker

  • Scenario: You have correctly configured your WebSphere Message Broker Toolkit to connect to a remote broker, but attempting to connect to the remote broker by using the WebSphere Message Broker Toolkit results in error MQRC 2059. You can connect to your remote broker from the same computer without error by using the WebSphere Message Broker Explorer, or by completing the following steps:
    1. Set the following environment variable:
      • On Windows: set MQSERVER=ChannelName/TCP/server-address(port)
      • On Linux: export MQSERVER=ChannelName/TCP/'server-address(port)'
    2. Open a WebSphere Message Broker command prompt, and enter the following test command:
      amqsputc queueName qmgrName
  • Explanation: The network configuration of your WebSphere Message Broker Toolkit installation is incorrect.
  • Solution:
    1. In the WebSphere Message Broker Toolkit, click Window > Preferences > General > Network Connection. The Preferences window opens, and the Network Connections preferences are displayed.
    2. From the Active Provider list, select Direct. For more information about the Active Provider setting, see the "Network Connections" topic in the Eclipse information center. You can now connect to your remote broker by using the WebSphere Message Broker Toolkit.

Connection to the broker is slow

  • Scenario: Connection to the broker is slow and you cannot complete other actions in the WebSphere Message Broker Toolkit when you request the following operations:
    • Creating a broker
    • Creating an execution group
    • Deploying a broker archive file, using the Deploy a BAR File wizard
    • Opening the Administration log editor
  • Solution: Click Cancel on the progress monitor dialog box to cancel the in-progress connection. Connection to the broker is canceled, so that you can perform other actions in the WebSphere Message Broker Toolkit. You can then resubmit the canceled operation.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:39


Task topicTask topic | Version 8.0.0.7 | au16601_