-XX:[+|-]JITCompilerContinuation (Option for the JIT compiler continuation functionality)
- Organization of this page
Format
- -XX:+JITCompilerContinuation
-
This option enables the JIT compiler continuation functionality.
- -XX:-JITCompilerContinuation
-
This option disables the JIT compiler continuation functionality.
Description
Specify whether to enable the JIT compiler continuation functionality.
Hitachi recommends that you enable this functionality to be able to continue an application normally even if the JIT compilation fails due to a logical inconsistency in a method configuring the application.
If you enable the JIT compiler continuation functionality, even if the JIT compilation fails due to a logical inconsistency in a method configuring the application, JavaVM outputs the log for this functionality to the JavaVM log file and continues the processing. In this case, the subsequent compilation with the method where the JIT compilation failed is executed using the interpreter method. From the methods configuring an application, the methods other than those where the JIT compilation failed are executed with the JIT compilation, so the application continues normally. However, if the JIT compilation fails six times or more, JavaVM outputs an error report file and a memory dump or core dump, and then terminates the processing forcefully.
If you disable the JIT compiler continuation functionality, and if the JIT compilation fails due to a logical inconsistency in a method configuring the application, JavaVM outputs an error report file and a memory dump or core dump, and then terminates the processing forcefully.
- Default value
-
-
-XX:+JITCompilerContinuation
-
- Prerequisite option
-
-
-server
-
-XX:+HitachiVerboseGC
-
Output format
[id]
- Note:
-
The log of the JIT compiler continuation functionality is output after [id].
A description of the output contents is as follows:
- id:
-
This option specifies the JCC (identifier of the JavaVM log file).
Example of output
[JCC][Thread: 0x05432c00]<Thu Nov 15 17:10:40 2012>[Method: jit_sample.func()V][Fail: 3][JITCT: 1] [JCC][Thread: 0x05432c00][PC: 0x083aff9a][Lib: D:\work\jdk\bin\server\jvm.dll+0x3aff9a][VM: Java HotSpot(TM) Server VM (20.8-b03-CDK0950-20121115 mixed mode windows-x86 )] [JCC][Thread: 0x05432c00][EAX=0x00000000, EBX=0x00618128, ECX=0x00000000, EDX=0x05485340] [JCC][Thread: 0x05432c00][ESP=0x0566d3c0, EBP=0x0566d3c4, ESI=0x00618278, EDI=0x00000000] [JCC][Thread: 0x05432c00][EIP=0x083aff9a, EFLAGS=0x00010202] [JCC][Thread: 0x05432c00][siginfo: read 0x00000000] [JCC][Thread: 0x05432c00][Unlock: MethodCompileQueue_lock] [JCC][Thread: 0x05432c00][NewJITCT: 0x05438800][JITCT: 2] [JCC][Thread: 0x05432c00][Free: "ResourceArea" 524288 bytes.] [JCC][Thread: 0x05432c00][stop] [JCC][Fail: 1][date: Thu Nov 15 10:10:40 2012][Method: jit_sample.func1(Ljava/lang/String;)V][PC: 0x083ff00a][Lib: D:\work\jdk\bin\server\jvm.dll+0x3ff00a] [JCC][Fail: 2][date: Thu Nov 15 11:11:16 2012][Method: jit_sample.func2()V][PC: 0x083afe3a][Lib: D:\work\jdk\bin\server\jvm.dll+0x3afe3a]