WMB/IIB MustGather: problems with the HTTP Listener (on Windows)

1. Consider following the Troubleshooting and support guide.


2. Read more about Working with HTTP flows.


3. Check for known issues:
   Resolving problems when you use HTTP and SOAP nodes
   

1. mqsidc

   See: mqsidc usage instructions
   

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


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


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


4. Abends
   It is possible that the component is abruptly ending.
   Check for abend files in the /MQSI_WORKPATH/common/errors directory.
   See: Abend files


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


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

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.