|
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:
- For releases of WebSphere Application Server V4.0 and
V5.0:
- For releases of WebSphere Application server V5.1:
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)
Note: Refer to Step 2E, "Traces: IBM HTTP
Server<-->WebSphere 4.0, 5.0, 5.1."
Lotus Domino
- Stop the Lotus Domino Server.
- Edit the plugin-cfg.xml file and change Loglevel to
Trace. For example:
<Log LogLevel="Trace"
Name="c:\WebSphere\AppServer\logs\http_plugin.log"/> |
 |
- Clear the plug-in log from the
install_root\logs directory.
- On the Application Server, set the following trace string:
- For releases of WebSphere Application Server v4.0:
- In the administrative client, select the Application Server in the
topology tree.
- Go to the Services tab and select Trace Service, then Edit
properties.
- In the Trace Service window, type the trace string:
com.ibm.ws.http*=all=enabled |
 |
- In the Trace Service window, also specify the output file with
the fully-qualified path.
- Click OK in the Trace Service window.
- Click Apply.
- For releases of WebSphere Application Server
v5.0 and v5.1:
- In the Administrative Console, expand the Troubleshooting section and
click Logs and Trace.
- Click on your server.
- Click Diagnostic Trace.
- In Trace Specification, type the following trace string:
Servlet_Engine=all=enabled:HTTP_Transport=all=enabled |
 |
- For Trace Output, choose File, then type a filename.
- Click Apply and save your configuration.
- Restart the Lotus Domino Server and the Application Server.
- Recreate the problem.
- Collect the following data files and information:
- plugin-cfg.xml
- native.log (for v4.0), http_plugin.log (for v5.0 and
v5.1)
- stderr and stdout
- TraceFile (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 |
 |
- Follow instructions to send
diagnostic information to IBM support.
Internet Information Services (IIS)
- Enable W3C Extended Logging in Internet Information Services
- Stop the Internet Information Services.
- Edit the plugin-cfg.xml file and change Loglevel to
Trace. For example:
<Log LogLevel="Trace"
Name="c:\WebSphere\AppServer\logs\http_plugin.log"/> |
 |
- Clear the plug-in log from the
install_root\logs directory.
- On the Application Server, set the following trace string:
- For releases of WebSphere Application Server
v4.0:
- In the administrative client, select the Application Server in the
topology tree.
- Go to the Services tab and select Trace Service, then Edit
properties.
- In the Trace Service window, type the trace string:
com.ibm.ws.http*=all=enabled |
 |
- In the Trace Service window, also specify the output file with
the fully-qualified path.
- Click OK in the Trace Service window.
- Click Apply.
- For releases of WebSphere Application Server
v5.0 and v5.1:
- In the Administrative Console, expand the Troubleshooting section and
click Logs and Trace.
- Click on your server.
- Click Diagnostic Trace.
- In Trace Specification, type the following trace string:
Servlet_Engine=all=enabled:HTTP_Transport=all=enabled |
 |
- For Trace Output, choose File and type a filename.
- Click Apply and save your configuration.
- Restart the Internet Information Services and the Application Server.
- Recreate the problem.
- Collect the following data files and information:
- plugin-cfg.xml
- native.log (for v4.0), http_plugin.log (for v5.0 and
v5.1)
- W3C Extended Log (ex*.log)
- The Win32.log or System32.log
- stderr and stdout
- TraceFile (from step 5)
- Internet Information Services 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 |
 |
- Follow instructions to send
diagnostic information to IBM support.
Sun ONE Web Server (formerly iPlanet)
- Stop the Sun ONE Web Server.
- Clear the access and error logs for the Sun ONE Web Server.
- Edit the plugin-cfg.xml file and change Loglevel to
Trace. For example:
<Log LogLevel="Trace"
Name="c:\WebSphere\AppServer\logs\http_plugin.log"/> |
 |
- Clear the plug-in log from the
install_root\logs directory.
- On the Application Server, set the following trace string:
- For releases of WebSphere Application Server
v4.0:
- In the administrative client, select the Application Server in the
topology tree.
- Go to the Services tab and select Trace Service, then Edit
properties.
- In the Trace Service window, type the trace string:
com.ibm.ws.http*=all=enabled |
 |
- In the Trace Service window, also specify the output file with
the fully-qualified path.
- Click OK in the Trace Service window.
- Click Apply.
- For releases of WebSphere Application Server
v5.0 and v5.1:
- In the Administrative Console, expand the Troubleshooting section and
click Logs and Trace.
- Click on your server.
- Click Diagnostic Trace.
- In Trace Specification, type the following trace string:
Servlet_Engine=all=enabled:HTTP_Transport=all=enabled |
 |
- For Trace Output, choose File and type a filename.
- Click Apply and save your configuration.
- Restart the Sun ONE Web Server and the Application Server.
- Recreate the problem.
- Collect the following data files and information:
- plugin-cfg.xml
- magnus.conf and obj.conf
- error and access logs from the Web server
- native.log (for v4.0) http_plugin.log (for v5.0 and
v5.1)
- stderr and stdout
- TraceFile (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 |
 |
- 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.
|
|
|