|
Problem(Abstract) |
Collecting data for problems with HTTP Status code 500
"Internal Server Error" or any WebSphere® Application Server V5.0 and 5.1
servlet engine and Web container errors logged in Application Server logs.
Gathering the information before calling IBM® support will help
familiarize you with the troubleshooting process and save you time. |
|
|
|
Resolving the
problem |
If you have already contacted support, continue on to the
Servlet Engine/Web Container MustGather information. Otherwise, refer to
MustGather:
Read first for all WebSphere Application Server products.
Servlet Engine and Web container specific MustGather information
If possible, provide a simple testcase that has no external depenancies.
If a testcase cannot be provided, collect the following data:
- Run genHistoryReport.bat or genHistoryReport.sh
which is located in the following directory:
install_root/bin |
|
The historyreport.html will be generated your
working directory. |
|
- Stop the Web server and delete all Web server logs and the
http_plugin.log file on the Web server system.
- If you suspect that the problem might be related to WebSphere
Application Server plug-in, or to Web server itself, enable full
plug-in trace.
- Important: Synchronize clocks on all Web server and WebSphere
Application Server systems.
- Clear all Application Server logs:
- native_stderr
- native_stdout
- SystemErr
- SystemOut
The log files are located in the following directory: |
|
install_root/logs/server_name |
|
Note: If you have configured to write Application
Server log files into a different location, then clear them
accordingly. |
|
- Clear all Application Server FFDC logs. FFDC files are located in the
following directory:
install_root/logs/ffdc |
|
Note: If you have configured to write FFDC log
files into a different location, then clear them accordingly. |
|
- Enable and collect Application Server traces with the following trace
string:
Servlet_Engine=all=enabled:HTTP_Transport=all=enabled |
|
For detailed instructions on enabling trace, see How
to setup a Trace. |
|
When you recreate problem
Capture the following data quickly:
- Capture a browser screen shot displaying the error. On windows press
<Alt>+<PrtSc> to capture the current browser window
into the clipboard. Paste that into a file.
- Collect the following documents and information:
- Were clocks synchronized?
- The Application Server logs such as the following:
- native_stderr
- native_stdout
- SystemErr
- SystemOut
- trace
- FFDC logs with the current date, located in the following directory:
- The server.xml file that is located in the directory:
install_root/config/cells/cell_name/nodes/
node_name/servers/server_name |
|
- The http_plugin.log file.
- The plugin-cfg.xml file.
- The Web server configuration files, such as httpd.conf for
IBM HTTP Server.
- The Web server logs, such as access and error logs
for IBM HTTP Server.
- Screen capture.
- The historyReport.html file from running
genHistoryReport.bat or genHistoryReport.sh
- Follow instructions to send
diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials
specific to the Servlet Engine/Web Container component, search the WebSphere
Application Server support site. |
|
|
|