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 when using the WebSphere Message Broker Explorer

Work through the advice provided to help you to deal with problems that can arise when you are using the WebSphere® Message Broker Explorer.

Tracing problems with accounting and statistics

  • Scenario: When you view accounting and statistics data using the WebSphere Message Broker Explorer you encounter a problem, and you want to collect trace.
  • Explanation: The WebSphere Message Broker Explorer uses the Java™ Message Service (JMS) to retrieve the accounting and statistics data from the broker. To trace problems with this connection, you must turn on JMS tracing in WebSphere MQ.
  • Solution: See the WebSphere MQ documentation for information about how to turn on JMS tracing. You can find this information in the following part of the information center: Using Java > Using WebSphere MQ classes for JMS > Solving problems > Tracing programs.

The Brokers folder is missing

  • Scenario: You have opened the WebSphere MQ Explorer to work with brokers and associated resources, but you cannot see the Brokers folder.
  • Explanation: The WebSphere Message Broker Explorer is an extension to the WebSphere MQ Explorer, and provides the Brokers folder and Broker Archive Files folder, and related actions. You must install the WebSphere Message Broker Explorer component on all computers on which you want to use the WebSphere MQ Explorer to manage WebSphere Message Broker resources, including brokers, execution groups and BAR files.
  • Solution: Close your MQ Explorer session, follow the instructions to install the WebSphere Message Broker Explorer, then start the MQ Explorer again.

You cannot open the information center on Red Hat Enterprise Linux

  • Scenario: You are using the WebSphere Message Broker Explorer on Red Hat Enterprise Linux Server 5.2 or Red Hat Enterprise Linux Server 5.3 but you cannot open the information center from inside WebSphere Message Broker Explorer.
  • Solution: Set the environment variable MOZILLA_FIVE_PATH then run the strmqcfg command. For more information, see the question about running the SWT browser inside Eclipse at: Eclipse SWT FAQ

Accounting and statistics do not work for a remote broker

  • Scenario: You try to view statistics, but instead see a message box:
    Could not connect to broker brokerName.
    Is MQ configured for JMS?
  • Explanation: Java Message Service (JMS) has not been correctly configured. Either JMS has not been enabled for the queue manager, or you do not have access to the channel that the broker uses for JMS activity. Check the log for more details. Note: In WebSphere MQ Version 7.0, 7.0.1, 7.1 and 7.5 onwards JMS is automatically configured, so the problem could be due to the security settings on the publish/subscribe queues. Verify that WebSphere Message Broker Explorer can communicate with the queue manager's publish/subscribe queues. For more information on WebSphere MQ publish/subscribe security, see IBM Education Assistant module: WebSphere MQ V7 Publish/subscribe security.
  • Solution: If the log shows that JMS has not been correctly set up, take the following steps:
    1. In a WebSphere Message Broker command console, change to the MBExplorerInstallLocation\eclipse\plugins\com.ibm.etools.wmadmin.broker.stats_releaseNumber directory.
    2. Run the following command:
      runmqsc queuemanager < setup_jms.mqsc
    If the log shows that you do not have permission to access the channel:
    1. Check which channel is being used by viewing the Statistics panel for the broker in WebSphere Message Broker Explorer. The channel is normally SYSTEM.DEF.SVRCONN.
    2. In a WebSphere Message Broker command console, issue the following command to allow any user on your broker machine, who is a member of the mqm and mqbrkrs groups, to run with the permissions of the broker user:
    alter chl (SYSTEM.DEF.SVRCONN) CHLTYPE(SVRCONN) MCAUSER(brokerUser)
    Note: Setting SYSTEM.DEF.SVRCONN MCAUSER(brokerUser) when the broker user is a member of the mqm group requires security protocols, such as Transport Layer Security (TLS), Secure Sockets Layer (SSL), channel authentication security, or a security exit, to be set up. For more information on security, see Security overview.

SYSTEM.DEF.SVRCONN error

  • Scenario: When you try to connect to a broker to view accounting and statistical information, an error message reports that WebSphere Message Broker Explorer cannot connect to SYSTEM.DEF.SVRCONN.
  • Explanation: This error might indicate that the SHARECNV parameter on the SVRCONN channel of the queue manager is not compatible with the current WebSphere MQ level of JMS.
  • Solution:
    1. For more information about the error, turn on service trace; see Changing trace settings from the WebSphere Message Broker Explorer.
    2. In WebSphere MQ Explorer, set Sharing Conversations (SHARECNV) to at least 1.
Notices | Trademarks | Downloads | Library | Support | Feedback

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

        
        Last updated:
        
        Last updated: 2016-05-23 14:48:28


Task topicTask topic | Version 8.0.0.7 | bu10550_