|
Problem(Abstract) |
When trying to determine the nature of a JIT failure, use
the attached script to start WebSphere® Application Server. |
|
|
|
Cause |
Failure converting Java™ bytecode to machine code
resulting in a WebSphere Application Server failure on Linux® |
|
|
Resolving the
problem |
To debug JIT failures, you must run multiple tests and
gather log files from each test.
- Copy the attached startJit50Linux.sh file to $WAS_HOME/bin
(/opt/WebSphere/AppServer/bin)
- Modify the startJit50Linux.sh file with the following changes:
- Determine what application server you are debugging and
modify the script. The script is set to debug server1.
- Create the following directory: /opt/JitDebug or modify
the script to reflect another location.
- Run the startJit50Linux.sh script, select an option and determine if
the crash still occurs.
- For each crash, run gdb against the core file, and provide the
requested files, then continue with the next test:
gdb -x gdb_commands.txt [JAVA_PATH]
[CORE_PATH] > gdbtrace_out.txt
where:
- [JAVA_PATH] is
/opt/WebSphere/AppServer/java/jre/bin/exe/java
- [CORE_PATH] is the path/filename for the core
file
- gdb_commands.txt is attached to this document
- For more information on gdb_commands.txt , refer to: MustGather:
Crash on Linux
- If running an option does not produce a failure, stop and contact IBM®
Support. Send the following files for each test:
- gdbtrace_out.out
- $WAS_HOME/bin/runhistory
- $WAS_HOME/bin/start.jit.log
- All files from /opt/JitDebug
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|