Troubleshooting
Problem
You are using WebSphere Message Broker (WMB) or IBM Integration Bus (IIB) and are having problems with the HTTP Listener (the biphttplistener process). 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
- Consider following the Troubleshooting and support guide.
- Read more about Working with HTTP flows.
- Check for known issues:
Resolving problems when you use HTTP and SOAP nodes
- mqsidc
See: mqsidc usage instructions
- When running the tool, select the option for 'Broker Collector', when prompted.
- Traces
Tracing the component will allow IBM Support to gain a better understanding of the problem.- An HTTP Listener Trace can be used to capture a problem during runtime.
- An HTTP Listener Startup trace can be used to capture problems that occur during the initialization of the component.
- Project Interchange files
IBM Support may need to understand how the HTTP Listener is being invoked.
- You can export your Message Flow and Message Set project(s) into an archive file for easy transmission.
See: Exporting your message flow projects from the Toolkit
- You can export your Message Flow and Message Set project(s) into an archive file for easy transmission.
- Abends
It is possible that the component is abruptly ending.
Check for abend files in the /MQSI_WORKPATH/common/errors directory.
See: Abend files - 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
- Record the WebSphere Message Broker version, release, and maintenance level.
- Listener Properties
- The broker-wide listener properties.
mqsireportproperties <broker> -b httplistener -o HTTPListener -r
mqsireportproperties <broker> -b httplistener -o HTTPConnector -r
mqsireportproperties <broker> -b httplistener -o HTTPSConnector -r - The embedded EG ("SOAP") listener properties.
mqsireportproperties <broker> -e <eg_name> -o HTTPConnector -r
mqsireportproperties <broker> -e <eg_name> -o HTTPSConnector -r
- The broker-wide listener properties.
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 IBM Integration Bus IIB IBMIB MQ Integrator WBIMB WBI-MB MQSI WMQI
Was this topic helpful?
Document Information
Modified date:
23 March 2020
UID
swg21299776