IBM Support

MustGather: WebSphere Application Server HTTP plug-in problems

Troubleshooting


Problem

Collecting data for IBM WebSphere Application Server HTTP plug-in problems with the IBM HTTP Server, Apache Server, Lotus Domino, Internet Information Services, and iPlanet (formerly Sun ONE Web Server). Gathering this information before calling IBM support helps familiarize you with the troubleshooting process and saves you time.

Resolving The Problem

Collecting data manually


If you already contacted support, continue to the component-specific MustGather information. Otherwise review this document: MustGather: Read first for WebSphere Application Server.

Problems encountered when using the WebSphere Application Server HTTP plug-in can be caused by an incorrect Web server or plugin-cfg.xml configuration. IBM recommends first reviewing the following documentation to assist in resolving problems related to the WebSphere Application Server HTTP plug-in:
 
IBM also maintains cumulative releases of the WebSphere Application Server HTTP plug-in module. Visit the Web server plug-in policy for WebSphere Application Server for more information on how to download the latest plug-in modules.

WebSphere Application Server HTTP plug-in specific MustGather
If you still have problems with the WebSphere Application Server HTTP plug-in, continue to gather the following MustGather information for the appropriate Web server:

 


IBM HTTP Server and Apache Server
Because the IBM HTTP Server is based on Apache Server, the MustGather needed to debug WebSphere Application Server HTTP plug-in problems is the same for both Web servers and is included in the following document:

MustGather: IBM HTTP Server Request Failures (for example,. 500, 404, 400, and so forth)
 


Lotus Domino
  1. Stop the Lotus Domino Server.
     
  2. Edit the plugin-cfg.xml file and change Loglevel to Trace. For example:

    <Log LogLevel="Trace" Name="c:\WebSphere\AppServer\logs\http_plugin.log"/>
     
  3. Clear the plug-in log from the install_root\logs directory.
     
  4. On the Application Server, set the following trace string:
    • For releases of WebSphere Application Server V8.5 and V9.0:
      1. In the administrative console, expand the Troubleshooting section and click on Logs and Trace.
         
      2. Click on your server.
         
      3. Click Change Log Detail Levels.
         
      4. In Trace Specification, type the following trace string (Note: This should be 1 line, but was broken up here for display purposes):

        *=info:com.ibm.ws.webcontainer*=all:com.ibm.wsspi.webcontainer*=all: HTTPChannel=all
         
      5. For Trace Output, choose File and type a file name.
         
      6. Click Apply and save your configuration.
      7. A network trace, please see for further details:Using packet trace tools iptrace, snoop, tcpdump, wireshark, and nettl
    • For releases of WebSphere Application Server V7.0 and V8.0:
      1. In the administrative console, expand the Troubleshooting section and click Logs and Trace.
         
      2. Click on your server.
         
      3. Click Change Log Detail Levels.
         
      4. In Trace Specification, type the following trace string (Note: This should be 1 line, but was broken up here for display purposes):

        *=info:com.ibm.ws.webcontainer*=all:com.ibm.wsspi.webcontainer*=all:HTTPChannel=all:GenericBNF=all:TCPChannel=all 

        Note: There should NOT be any spaces or '.' between webcontainer and '*' for the above trace strings.
      5. For Trace Output, choose File and type a file name.
         
      6. Click Apply and save your configuration.
      7. A network trace, please see for further details:Using packet trace tools iptrace, snoop, tcpdump, wireshark, and nettl
         
  5. Restart the Lotus Domino Server and the Application Server.
     
  6. Recreate the problem.
     
  7. Collect the following data files and information:
    • plugin-cfg.xml
    • http_plugin.log
    • stderr and stdout
    • Trace file (from step 4)
    • Lotus Domino version
    • The date and time of failure
    • The browser version
    • The full URL that resulted in failure. For example:


      http://www.mycompany.com/mystuff/goodies/index.html


       
  8. Follow instructions to send diagnostic information to IBM support.
 


Internet Information Services (IIS)
  1. Stop the IIS Web Server
     
  2. Edit the plugin-cfg.xml file and change Loglevel to Trace. For example:

    <Log LogLevel="Trace" Name="C:\IBM\WebSphere\Plugins\logs\http_plugin.log"/>
     
  3. Clear the plug-in log from the install_root\logs directory.
     
  4. On the Application Server, set the following trace string:
    • For releases of WebSphere Application Server V8.5 and V9.0:
      1. In the administrative console, expand the Troubleshooting section and click Logs and Trace.
         
      2. Click on your server.
         
      3. Click Change Log Detail Levels.
         
      4. In Trace Specification, type the following trace string (Note: This should be 1 line, but was broken up here for display purposes):

        *=info:com.ibm.ws.webcontainer*=all:com.ibm.wsspi.webcontainer*=all: HTTPChannel=all
         
      5. For Trace Output, choose File and type a file name.
         
      6. Click Apply and save your configuration.
      7. A network trace, please see for further details:Using packet trace tools iptrace, snoop, tcpdump, wireshark, and nettl
    • For releases of WebSphere Application Server V7.0 and V8.0:
      1. In the administrative console, expand the Troubleshooting section and click Logs and Trace.
         
      2. Click on your server.
         
      3. Click Change Log Detail Levels.
         
      4. In Trace Specification, type the following trace string (Note: This should be 1 line, but was broken up here for display purposes):


        *=info:com.ibm.ws.webcontainer*=all:com.ibm.wsspi.webcontainer*=all:HTTPChannel=all:GenericBNF=all:TCPChannel=all 

        Note: There should NOT be any spaces or '.' between webcontainer and '*' for the above trace strings.
      5. For Trace Output, choose File and type a file name.
         
      6. Click Apply and save your configuration.
      7. A network trace, please see for further details:Using packet trace tools iptrace, snoop, tcpdump, wireshark, and nettl
         
  5. Restart the IIS Web Server and the Application Server.
     
  6. Recreate the problem.
     
  7. Collect the following data files and information:
    • plugin-cfg.xml
    • config file for IIS
    • IIS 6 (Windows 2003)
      • metabase.xml
      • default path= C:\Windows\System32\inetsrv\metabase.xml
    • IIS 7 (Windows 2008, Windows 7)
      • applicationHost.config
      • default path= C:\Windows\System32\inetsrv\config\applicationHost.config
    • IIS 8 (Windows 2012, Windows 8)
      • applicationHost.config
      • default path= C:\Windows\System32\inetsrv\config\applicationHost.config
    • http.plugin.log
    • IIS Log (u_ex*.log or ex*.log)
    • stderr and stdout
    • Trace file (from step 4)
    • Internet Information Services version
    • Any corresponding errors seen in the Event Viewer > Windows Logs > Application listing. Save as*.evtx
    • The date and time of failure
    • The browser version
    • The full URL that resulted in failure. For example:

      http://www.mycompany.com/mystuff/goodies/index.html
  8. Follow instructions to send diagnostic information to IBM support
 


Oracle iPlanet Web Server (formerly Sun ONE)
  1. Stop the Oracle iPlanet Web Server.
     
  2. Clear the access and error logs for the Oracle iPlanet Web Server.
     
  3. Edit the plugin-cfg.xml file and change Loglevel to Trace. For example:

    <Log LogLevel="Trace" Name="C:\IBM\WebSphere\Plugins\logs\http_plugin.log"/>
     
  4. Clear the plug-in log from the install_root\logs directory.
     
  5. On the Application Server, set the following trace string:
    • For releases of WebSphere Application Server V8.5 and V9.0:
      1. In the administrative console, expand the Troubleshooting section and click Logs and Trace.
      2. Click on your server.
         
      3. Click Change Log Detail Levels.
         
      4. In Trace Specification, type the following trace string (Note: This should be 1 line, but was broken up here for display purposes):

        *=info:com.ibm.ws.webcontainer*=all:com.ibm.wsspi.webcontainer*=all: HTTPChannel=all

         
      5. For Trace Output, choose File and type a file name.
         
      6. Click Apply and save your configuration.
      7. A network trace, please see for further details:Using packet trace tools iptrace, snoop, tcpdump, wireshark, and nettl
    • For releases of WebSphere Application Server V7.0 and V8.0:
      1. In the administrative console, expand the Troubleshooting section and click Logs and Trace.
         
      2. Click on your server.
         
      3. Click Change Log Detail Levels.
      4. In Trace Specification, type the following trace string (Note: This should be 1 line, but was broken up here for display purposes):


        *=info:com.ibm.ws.webcontainer*=all:com.ibm.wsspi.webcontainer*=all:HTTPChannel=all:GenericBNF=all:TCPChannel=all 

        Note: There should NOT be any spaces or '.' between webcontainer and '*' for the above trace strings.
      5. For Trace Output, choose File and type a file name.
      6. Click Apply and save your configuration.
      7. A network trace, please see for further details:Using packet trace tools iptrace, snoop, tcpdump, wireshark, and nettl
  6. Restart the Oracle iPlanet Web Server and the Application Server.
     
  7. Recreate the problem.
     
  8. Collect the following data files and information:
    • plugin-cfg.xml
    • magnus.conf and obj.conf
    • error and access logs from the Web server
    • http_plugin.log
    • stderr and stdout
    • Trace file (from step 5)
    • Sun ONE Web Server version
    • The date and time of failure
    • The browser version
    • The full URL that resulted in failure. For example:

      http://www.mycompany.com/mystuff/goodies/index.html
  9. Follow instructions to send diagnostic information to IBM support.

For a listing of all technotes, downloads, and educational materials specific to the Plug-in component, search the WebSphere Application Server support site.

Related information
Submitting information to IBM support
Steps to get support
MustGather: Read first
Troubleshooting guide
Tracing Intelligent Management feature in WebSphere Plug-in 8.5.5

 


Exchanging data with IBM Support

To diagnose or identify a problem, it is sometimes necessary to provide Technical Support with data and information from your system. In addition, Technical Support might also need to provide you with tools or utilities to be used in problem determination. You can submit files using one of following methods to help speed problem diagnosis:


Read first and related MustGathers

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Component":"Plug-in","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.0.0.0;8.5;8.0;7.0","Edition":"Base;Network Deployment","Line of Business":{"code":"LOB36","label":"IBM Automation"}},{"Product":{"code":"SS7JFU","label":"WebSphere Application Server - Express"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Component":"Plugin","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
09 September 2021

UID

swg21174894