Debugging Just In Time compiler failures
 Technote (troubleshooting)
 
Problem(Abstract)
When debugging a Just In Time (JIT) compiler failure on Microsoft® Windows®, AIX®, or Linux® for IBM® WebSphere® Application Server V5.0 releases, use the following procedures to gather JIT failure information for determination of a temporary workaround.
 
Resolving the problem
In order to debug JIT failures and determine a temporary work around, begin by setting the following Environment Entries:
To set the following Environment Entries from the administrative console:
Select Servers > Application Servers > server_name> Process Definition > Environment Entries > New

Add the following Name and Value pairs:

Name Value
JITC_COMPILEOPT COMPILING
JITC_COMPILING path_and_filename

Important: Make sure that you save changes to the master configuration.

Reproduce your problem and supply the information needed for IBM® Support to help resolve the problem, see MustGather instructions for "Crash" in the MustGather: Readme First.

Determine a failing method to skip, as a temporary workaround, by having a support representative review the compiling output and the JIT Problem Determination guide.

Modify the Environment Entry set above with the SKIP option:
Operating
System
Name Value
Windows JITC_COMPILEOPT COMPILING;SKIP
{failingPackage/failingClass}
{failingMethod}
AIX
Linux
JITC_COMPILEOPT COMPILING:SKIP
{failingPackage/failingClass}
{failingMethod}
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Java SDK
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1083960
IBM Group: Software Group
Modified date: Nov 10, 2005