|
Problem |
This document lists what is needed to debug a 404 error on
WebSphere® Application Server V4.0 releases. |
|
Solution |
If the 404 error is easily reproducible, do the
following:
- In the administrative console, select the Application
Server in the topology tree.
- Go to the Services tab and select Trace Service, and
then Edit properties.
- In the Trace Service window, specify the trace string:
com.ibm.servlet.engine.*=all=enabled
- In the Trace Service window, specify the output file
with the fully qualified path
- Click OK in the Trace Service window
- Click Apply
- Stop the application server
- Enable a plugin trace by changing the LogLevel variable from
Error to Trace in the plugin-cfg.xml file. This file is
found in \WebSphere\Appserver\config. The output file name is also
specified in this file. By default, the plugin trace file is native.log.
Regenerating the plugin sets the LogLevel back to
Error
- Stop the Web server
- Start the application server
- Start the Web server
- Recreate the problem and take a screen shot of the 404 error in the
browser
- Make the request directly to the servlet engine transport port and
bypass the plugin by going to 9080 or other defined port for the
webcontainer.
- In the administrative console, export the enterprise application that
encounters the 404 error:
- Right click on the enterprise application and choose Export
Application
- Select the directory you want the exported EAR to be placed
into
- Click OK"
- Send in the following files:
- Trace from steps 3 and 4
- stderr log
- stdout log
- native.log (this is the plugin trace)
- plugin-cfg.xml
- current XMLConfig export
- Document the requested URL, including the host and port the request is
made on.
- Screen shot of 404 error in the browser
- access and error log from the Web server
- Exported EAR file from step 14
If the 404 error is not easily reproducible and you cannot setup
tracing, do the following:
- Take a screen shot of the 404 error in the browser
- Make the request directly to the servlet engine transport port,
bypassing the plugin by going to 9080 or other defined port for the
webcontainer.
- In the administrative console, export the enterprise application that
is causing the 404 error:
- Right click on the enterprise application and select Export
Application
- Select the directory you want the exported EAR to be placed
into
- Click OK"
- Send in the following files:
- stderr log
- stdout log
- native.log (this is the plugin trace)
- plugin-cfg.xml
- current XMLConfig export
- Document the requested URL that causes the 404 error, including the
host and port number.
- Screen shot of 404 error in the browser
- access and error log from the Web server
- Exported EAR file from step 3
|
|
|
|
|
|
|