|
| Problem | This document lists what is needed to debug a 404 error in WebSphereŽ Application Server V3.5 releases. | | | | Solution | If the 404 error is easily reproducible, do the following:
- Start the administrative console:
- Click on the advanced tab of the servlet engine,
- Click on Settings,
- Select all options in the field Select Log File Mask,
- Click on OK, then
- Click on apply.
- While in the administrative console,
- Select your Application Server (for example Default Server), and
- Click on the advanced tab.
- Edit the Trace specification and "Trace output file settings.
- Set the Trace specification to the following value:
com.ibm.servlet.engine.*=all=enabled
- For trace output file, fill in the fully qualified filename. For example: c:/WebSphere/AppServer/logs/srttrace.txt
- Edit the bootstrap.properties on the Web server system to look like the following:
ose.native.log.level=ERROR|WARNING|TRACE|INFORM
ose.plugin.log.level=ERROR|WARNING|TRACE|INFORM
- Stop the Application Server
- Delete the stdout and stderr log files for the Application Server.
- Stop the Web server.
- Delete the error.log and access.log for 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.
- Send in the following files:
- Trace file from step 3.
- Everything in the $WAS_HOME/logs directory, ensuring that the stdout and stderr for the application server are included.
- Plug-in trace (trace.log.Web server.timestamp)
- Web server error.log
- Web server httpd.conf
- Web server access.log
- Application server rules.properties
- Application server bootstrap.properties
- XMLConfig export file
- Document the requested URL that causes the 404 error, including the host and port number.
- Screen shot of 404 error in the browser.
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
- Send in the following files:
- Everything in the install_root/logs directory, ensuring that the stdout and stderr for the Application Server are included.
- Plug-in log (trace.log.Web server.timestamp)
- Web server error.log
- Web server httpd.conf
- Web server access.log
- Application Server rules.properties
- Application Server bootstrap.properties
- XMLConfig export file
- Document the requested URL that causes the 404 error, including the host and port number.
- Screen shot of 404 error in the browser.
| | | | |
| |
|
Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Servlet Engine/Web Container Operating system(s): AIX, HPUX, Linux, Solaris, Windows Software version: 3.5, 3.5.1, 3.5.2, 3.5.3, 3.5.4, 3.5.4.1, 3.5.4.2, 3.5.5, 3.5.6, 3.5.7 Software edition: Advanced, Standard Reference #: 1143592 IBM Group: Software Group Modified date: 2004-10-27
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
|