WMB/IIB MustGather: problems with runtime message processing (on UNIX and Linux)

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:
   Resolving problems when developing message models
   Resolving problems when developing message flows

   Dynamic guide to troubleshooting Message Broker

   
   IIB and WMB Frequently Asked Questions
   Resolving problems when processing messages
   WebSphere Message Broker support site
   

1. mqsidc
   See: mqsidc usage instructions
   
   • When running the tool, select the option for 'Broker Collector', when prompted.


2. Abend files
   
   • Some runtime failures cause an abend. The syslog (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


3. 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


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

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:

• 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

• Use IBM Service Request to open or view a problem record with IBM.
• Send your data to IBM for further analysis.