Debugging JIT failures on Microsoft Windows for V3.5 and V4.0 releases

Technote (FAQ)
Problem
When trying to determine the nature of a JIT compiler failure on Microsoft® Windows®, 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.
  1. Copy the attached startJit.bat file to:

    install_root/bin

  2. To run the script from a command prompt, enter the script name and an option (1-4).

    Example:

    c:\WebSphere\AppServer\bin\startJit.bat 1 > test1.log 2>&1

    Option
    Optimization
    Definition
    1
    NMMI2JIT
    Disables in method transfer
    2
    NINLINING
    Disables method Inlining
    3
    NQOPTIMIZE
    Disables quadruple optimization
    4
    NALL
    Disables optimzation but not compilation
  3. If running an option does not produce a failure, stop and contact support. If a failure occurs, restart the test and select the next option.

Please send in the following files after all of the tests are complete:

  • All files from c:\JitDebug

  • stderr and stdout files from the Application Server











    Document Information

    Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Java SDK
    Operating system(s): Windows 2000, Windows NT, Windows XP
    Software version: 3.5, 4.0
    Software edition: Advanced
    Reference #: 1116527
    IBM Group: Software Group
    Modified date: 2004-12-01