Troubleshooting
Problem
You are using WebSphere Message Broker (WMB) or IBM Integration Bus (IIB) and are seeing behavior problems or errors with the processing of your messages on the Broker runtime. 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 share that data with IBM support.
Environment
These instructions are for WebSphere Message Broker or IBM Integration Bus on Windows systems.
Return to the WMB / IIB MustGather index for other systems.
Resolving The Problem
- Consider Using the Test Client in trace and debug mode.
- 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. - Check for known issues:
Resolving problems when developing message models
Resolving problems when developing message flowsDynamic guide to troubleshooting Message Broker
IIB and WMB Frequently Asked Questions
Resolving problems when processing messages
WebSphere Message Broker support site
- mqsidc
See: mqsidc usage instructions
- When running the tool, select the option for 'Broker Collector', when prompted.
- Abend files
- Some runtime failures cause an abend. The Windows Application Event Log (see below) will record the time and location of any *.abend files created.
You can also manually check for abend files in the directory: {MQSI_WORKPATH}\common\errors
- Some runtime failures cause an abend. The Windows Application Event Log (see below) will record the time and location of any *.abend files created.
- Project Interchange files for the problematic flow/set/ESQL/model
- You can export your Message Flow and Message Set project(s) into an archive file for easy transmission to IBM Support.
See: Exporting files from the Workbench
- You can export your Message Flow and Message Set project(s) into an archive file for easy transmission to IBM Support.
- 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.
- 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 Window systems, the local error log is the Windows Application Event Log.
You can find the Event Viewer from the Windows Control Panel.
See: Event viewer logs - Collect the Standard Output/Error logs.
On Window systems, WMB writes information to a 'console.out' file.
This file is located under the Message Broker workpath.
See: Standard System Logs
- Record the WebSphere Message Broker version, release, and maintenance level.
ATTENTION: A good problem description is one of the most important tools IBM needs to analyze your data!
When sending data to IBM, be sure to update your PMR or send a note with the following information:
- Use IBM Service Request to open or view a problem record with IBM.
- Send your data to IBM for further analysis.
Please see the IBM Software Support Handbook for more information on working with IBM support.
Product Synonym
WMB MB WebSphere Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI
Was this topic helpful?
Document Information
Modified date:
23 March 2020
UID
swg21299468