MustGather: WebSphere Application Server HTTP plug-in problems
 Technote (FAQ)
 
Problem
MustGather for WebSphere® Application Server HTTP plug-in problems with the IBM® HTTP Server, Apache Server, Lotus® Domino®, Internet Information Services, and Sun® ONE Web Server (formerly iPlanet). Gathering this information before calling IBM support helps familiarize you with the troubleshooting process and saves you time.
 
Solution
If you already contacted support, continue to the component-specific MustGather information. Otherwise, click: MustGather: Read first for all WebSphere Application Server products.

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
Lotus Domino
Internet Information Services (IIS)
Sun ONE Web Server (formerly iPlanet)



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)

Note: Refer to Step 2E, "Traces: IBM HTTP Server<-->WebSphere 4.0, 5.0, 5.1."


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 v4.0:
      1. In the administrative client, select the Application Server in the topology tree.

      2. Go to the Services tab and select Trace Service, then Edit properties.

      3. In the Trace Service window, type the trace string:

        com.ibm.ws.http*=all=enabled

      4. In the Trace Service window, also specify the output file with the fully-qualified path.

      5. Click OK in the Trace Service window.

      6. Click Apply.

    • For releases of WebSphere Application Server v5.0 and v5.1:
      1. In the Administrative Console, expand the Troubleshooting section and click Logs and Trace.

      2. Click on your server.

      3. Click Diagnostic Trace.

      4. In Trace Specification, type the following trace string:

        Servlet_Engine=all=enabled:HTTP_Transport=all=enabled

      5. For Trace Output, choose File, then type a filename.

      6. Click Apply and save your configuration.

  5. Restart the Lotus Domino Server and the Application Server.

  6. Recreate the problem.

  7. Collect the following data files and information:
    1. plugin-cfg.xml
    2. native.log (for v4.0), http_plugin.log (for v5.0 and v5.1)
    3. stderr and stdout
    4. TraceFile (from step 4)
    5. Lotus Domino version.
    6. The date and time of failure.
    7. The browser version.
    8. 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. Enable W3C Extended Logging in Internet Information Services
  2. Stop the Internet Information Services.

  3. Edit the plugin-cfg.xml file and change Loglevel to Trace. For example:

    <Log LogLevel="Trace" Name="c:\WebSphere\AppServer\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 v4.0:
      1. In the administrative client, select the Application Server in the topology tree.

      2. Go to the Services tab and select Trace Service, then Edit properties.

      3. In the Trace Service window, type the trace string:

        com.ibm.ws.http*=all=enabled

      4. In the Trace Service window, also specify the output file with the fully-qualified path.

      5. Click OK in the Trace Service window.

      6. Click Apply.

    • For releases of WebSphere Application Server v5.0 and v5.1:
      1. In the Administrative Console, expand the Troubleshooting section and click Logs and Trace.

      2. Click on your server.

      3. Click Diagnostic Trace.

      4. In Trace Specification, type the following trace string:

        Servlet_Engine=all=enabled:HTTP_Transport=all=enabled

      5. For Trace Output, choose File and type a filename.

      6. Click Apply and save your configuration.

  6. Restart the Internet Information Services and the Application Server.

  7. Recreate the problem.

  8. Collect the following data files and information:
    1. plugin-cfg.xml
    2. native.log (for v4.0), http_plugin.log (for v5.0 and v5.1)
    3. W3C Extended Log (ex*.log)
    4. The Win32.log or System32.log
    5. stderr and stdout
    6. TraceFile (from step 5)
    7. Internet Information Services version.
    8. The date and time of failure.
    9. The browser version.
    10. 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.


Sun ONE Web Server (formerly iPlanet)
  1. Stop the Sun ONE Web Server.

  2. Clear the access and error logs for the Sun ONE Web Server.

  3. Edit the plugin-cfg.xml file and change Loglevel to Trace. For example:

    <Log LogLevel="Trace" Name="c:\WebSphere\AppServer\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 v4.0:
      1. In the administrative client, select the Application Server in the topology tree.

      2. Go to the Services tab and select Trace Service, then Edit properties.

      3. In the Trace Service window, type the trace string:

        com.ibm.ws.http*=all=enabled

      4. In the Trace Service window, also specify the output file with the fully-qualified path.

      5. Click OK in the Trace Service window.

      6. Click Apply.

    • For releases of WebSphere Application Server v5.0 and v5.1:
      1. In the Administrative Console, expand the Troubleshooting section and click Logs and Trace.

      2. Click on your server.

      3. Click Diagnostic Trace.

      4. In Trace Specification, type the following trace string:

        Servlet_Engine=all=enabled:HTTP_Transport=all=enabled

      5. For Trace Output, choose File and type a filename.

      6. Click Apply and save your configuration.

  6. Restart the Sun ONE Web Server and the Application Server.

  7. Recreate the problem.

  8. Collect the following data files and information:
    1. plugin-cfg.xml
    2. magnus.conf and obj.conf
    3. error and access logs from the Web server
    4. native.log (for v4.0) http_plugin.log (for v5.0 and v5.1)
    5. stderr and stdout
    6. TraceFile (from step 5)
    7. Sun ONE Web Server version.
    8. The date and time of failure.
    9. The browser version.
    10. 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 getting support
MustGather: Read first
Troubleshooting guide
 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Plug-in
Operating system(s): Windows
Software version: 5.1
Software edition:
Reference #: 1174894
IBM Group: Software Group
Modified date: Mar 18, 2005