|
| Problem | When trying to determine the cause of a JIT failure on AIX®, use the attached script to start WebSphere® Application Server. | | | | Solution | In order to debug JIT failures, it is necessary to run multiple tests and gather log files from each test.
Verify that your Java™ 2 SDK meets the following criteria:- ca1.2.2-20011020 or later
- ca1.3.0-20010615 or later
- 1.3.1 All levels
- Copy the attached startJit.sh file to the directory install_root/bin (for example: /usr/WebSphere/AppServer/bin).
- Modify the startJit.sh file with the following changes:
Create the following directory: /usr/JitDebug or modify the script to reflect another location.
- Run the startJit.sh script, select an option and determine if the crash still occurs.
- For each crash, run the kca command against the core file, and provide the requested files, then continue with the next test. For more information on kca, refer to MustGather: Crash on AIX.
- If running an option does not produce a failure stop and contact support.
For each test, submit the following diagnostic information to IBM Support:- Standard data file format (SDFF) files.
- kca.out
- core-libs.tar.Z (this file is generated as a result of executing step 4)
- Renamed core file.
- install_root/bin/runhistory
- install_root/bin/start.jit.log
- All files from the directory, /usr/JitDebug.
| | | |  |
| |
|
Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Java SDK Operating system(s): AIX 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, 4.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, 4.0.7 Software edition: Advanced Reference #: 1116526 IBM Group: Software Group Modified date: 2004-06-02
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
|