IBM Support

MustGather: Channel Framework problems in WebSphere Application Server and WebSphere Liberty

Troubleshooting


Problem

Collecting data for problems in the HTTP and TCP Channel Framework component.  Gathering this MustGather information before engaging IBM support will help familiarize you with the troubleshooting process and save you time.

Resolving The Problem

  • Channel Framework MustGather Information

    Collect the following data.
    1. Run genHistoryReport.bat or genHistoryReport.sh, which is located in the following directory:
      install_root/profiles/profile_name/bin
    2. If you suspect that the problem involves the IBM webserver (IHS/plugin), get the MustGather: Request failures accessing WebSphere Application Server dynamic content through IBM HTTP Server in addition to the application server Channel Framework trace. 
    3. If you suspect that the problem involves the network between the IBM WebSphere Application Server (WAS) and the IBM webserver (IHS/plugin), get a RAW packet trace on both WAS and IHS in addition to the application server Channel Framework trace.
    4. Gather the HTTP and TCP Channel trace on Traditional WebSphere Application Server or WebSphere Liberty (See the next sections for the instructions and the trace strings).
  • Enable the HTTP and TCP Channel trace on Traditional WebSphere Application Server

    Enable the following Trace Specification:
    *=info:HTTPChannel=all:TCPChannel=all:GenericBNF=all
    For the detailed instructions on enabling this trace, see How to setup a trace in WAS.
    Notes:
    - Make sure to set the trace file size to 100 MB and the maximum historical number of trace files to 10.
    - Prior to getting the above trace, make backup and remove all the existing Websphere Application Server log, trace, and FFDC files. 
    - Make sure to stop the trace as soon as the problem is recreated or captured so that the trace files are not overwritten.
    2. Recreate the problem.
    3. Stop the trace as soon as the problem is recreated.
    3. Issue the collector.sh/collector.bat command in the directory install_root/bin from outside of WebSphere (e.g. /temp directory) to generate the server collector jar file. For the detailed instructions on generating the server collector jar file, see Gathering information with the collector tool.
  • Enable the HTTP and TCP Channel trace on WebSphere Liberty
    1. Open the server.xml file located within the <LIBERTY_HOME>/usr/servers/<server name>/ directory.

    2. Add (or update if it already exists) the following <logging> element:
    <logging traceSpecification="HTTPChannel=all:GenericBNF=all:HTTPDispatcher=all:TCPChannel=all" traceFileName="trace.log" maxFileSize="100" maxFiles="10" traceFormat="BASIC" />
     
    3. Make backup and remove the existing log and FFDC files within the <LIBERTY_HOME>/usr/servers/<server name>/logs directory

    4. Stop the Liberty server, then start the Liberty server with the --clean parameter:
        server start <SERVER_NAME> --clean

    5. Recreate the problem.

    6. Stop the trace as soon as the problem is recreated.

    7. Run the following command from the bin directory:

        server dump <SERVER_NAME>

    This will create a .zip file in the /usr/servers/<SERVER_NAME>/ directory.

  • Collect the following data when the problem is recreated
    Traditional WebSphere Application Server:
    1. Note down the error that you're troubleshooting.
    2. Collect the following documents and information:
      • The WebSphere Application Server log and trace files from the following directory:
        install_root/profiles/profile_name/logs/server_name
      • The FFDC files with the current date from the following directory:
        install_root/profiles/profile_name/logs/ffdc
      • The IHS/plugin configuration and log/trace files requested in the IHS mustgather (if collected)
      • The RAW packet trace (if collected)
      • The historyReport.html file from running genHistoryReport.bat or genHistoryReport.sh
      • The collector jar file
    WebSphere Liberty:
    1. Note down the error that you're troubleshooting.
    2. Collect the server dump zip file in the /usr/servers/<SERVER_NAME/ directory that is created by the server dump.  Note that if you configured the server to write the log and trace file to a different directory than the default /usr/servers/server_name/logs, then collect the log and trace files from the custom directory as well.
  • Exchange collected data with IBM Support
    You can submit collected data to IBM support by using one of the following methods:
    • Service Request (SR)
    • Email
    • FTP to the Enhanced Customer Data Repository (EcuRep)

[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"ARM Category":[{"code":"a8m50000000Cd4tAAC","label":"WebSphere Application Server traditional-All Platforms-\u003EChannel Framework-\u003ECHF Data Collection \u0026 Useful Docs"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"All Versions"}]

Document Information

Modified date:
13 March 2023

UID

swg21592086

Page Feedback