Troubleshooting an HTTP status code 404: "NOT FOUND" error
 Technote (FAQ)
 
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:

  1. In the administrative console, select the Application Server in the topology tree.

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

  3. In the Trace Service window, specify the trace string: com.ibm.servlet.engine.*=all=enabled

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

  5. Click OK in the Trace Service window

  6. Click Apply

  7. Stop the application server

  8. 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

  9. Stop the Web server

  10. Start the application server

  11. Start the Web server

  12. Recreate the problem and take a screen shot of the 404 error in the browser

  13. 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.

  14. In the administrative console, export the enterprise application that encounters the 404 error:

    1. Right click on the enterprise application and choose Export Application

    2. Select the directory you want the exported EAR to be placed into

    3. Click OK"

  15. Send in the following files:

    1. Trace from steps 3 and 4

    2. stderr log

    3. stdout log

    4. native.log (this is the plugin trace)

    5. plugin-cfg.xml

    6. current XMLConfig export

    7. Document the requested URL, including the host and port the request is made on.

    8. Screen shot of 404 error in the browser

    9. access and error log from the Web server

    10. Exported EAR file from step 14

If the 404 error is not easily reproducible and you cannot setup tracing, do the following:

  1. Take a screen shot of the 404 error in the browser

  2. Make the request directly to the servlet engine transport port, bypassing the plugin by going to 9080 or other defined port for the webcontainer.

  3. In the administrative console, export the enterprise application that is causing the 404 error:

    1. Right click on the enterprise application and select Export Application

    2. Select the directory you want the exported EAR to be placed into

    3. Click OK"

  4. Send in the following files:

    1. stderr log

    2. stdout log

    3. native.log (this is the plugin trace)

    4. plugin-cfg.xml

    5. current XMLConfig export

    6. Document the requested URL that causes the 404 error, including the host and port number.

    7. Screen shot of 404 error in the browser

    8. access and error log from the Web server

    9. Exported EAR file from step 3
 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Servlet Engine/Web Container
Operating system(s): HP-UX
Software version: 4.0.7
Software edition:
Reference #: 1116535
IBM Group: Software Group
Modified date: Aug 31, 2005