IBM Support

WMB/IIB MustGather: Problems with JMS (on UNIX and Linux)

Troubleshooting


Problem

You are designing an application solution with WebSphere Message Broker (WMB) and IBM Integration Bus (IIB) and are having problems with JMS. This MustGather document explains how to troubleshoot this problem by yourself, how to generate diagnostic data when the problem is happening, how to collect the available data from your system, and how to share that data with IBM support.

Environment

These instructions are for WebSphere Message Broker or IBM Integration Bus on AIX, HP-UX, Linux, and Solaris systems.
Return to the WMB / IIB MustGather index for other systems.

Resolving The Problem


Step 1: Self-guided Troubleshooting


  1. Consider Using the Test Client in trace and debug mode.

  2. A user level trace is intended to assist users with understanding how their ESQL is processed.
    It will also show a high level view of the message flow behavior.

  3. Check for known issues:
    Troubleshooting JMS nodes
    developerWorks Forums: WebSphere Message Broker: JMS
    WebSphere Message Broker support site


Step 2: Collect Data


  1. mqsidc

    See: mqsidc usage instructions

    • When running the tool, select the option for 'Broker Collector', when prompted.


  2. JMS details
    Export a current view of your JMS configuration with these items:
    • mqsireportproperties <broker> -c JMSProviders -o <JMSProvider> -r
    • the contents of the jarsURL directory
    • the JNDI bindings file

  3. Project Interchange files for the problematic flow/set/ESQL/model

  4. Traces If the problem occurs during a runtime test or with the Toolkit test facility, WMB execution group traces can be used to gain a better understanding of the problem.
    • A user level trace is intended to assist users with understanding how their ESQL is processed. It will also show a high level view of the message flow behavior.
    • A service level trace is intended to be provided to IBM Support to assist in the diagnosis of your issue.

  5. General Broker information
    If the mqsidc tool was not run, then capture this information manually
    • Record the WebSphere Message Broker version, release, and maintenance level.
      This can be captured using the command 'mqsiservice -v'.
    • Record the operating system version, release, and maintenance level.
    • Record the version, release, and maintenance level of any related products and components for the problematic application.
    • Collect the local error log.
      On UNIX and Linux systems, the local error log is the syslog.
      The location of your syslog is configured in the syslog daemon.
      See: Configuring the syslog daemon
    • Collect the Standard Output/Error logs.
      On UNIX and Linux systems, WMB writes information to both 'stdout' and 'stderr' files.
      These files are located under the Message Broker workpath.
      See: Standard System Logs


  • Tell us what errors you saw, where you saw them, and what time they happened
  • Let us know if you made any changes to WebSphere Message Broker or the system before the problem
  • Share any other observations which you think will help us to better understand the problem

Step 3: Submit Data to IBM






Please see the IBM Software Support Handbook for more information on working with IBM support.



[{"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Java \/ JMS","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"10.0;9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Product Synonym

WMB MB WBIMB

Document Information

Modified date:
23 March 2020

UID

swg21299796