JITM messages
JIT compiler messages.
JVMJITM000E Unsupported hardware [%d].
Explanation
The current hardware is not supported by the compiler.System action
The compiler does not generate code for this hardware.User response
Check the IBM® Java documentation for a list of supported hardware.JVMJITM001W No more space for AOT code in shared class cache. New AOT code will not be generated.
Explanation
The AOT section of the shared class cache is full.System action
The compiler stops generating AOT code. The AOT code already stored in the shared class cache continues to be used.User response
Increase the size of the AOT section of the shared class cache using the -Xscmaxaot option.JVMJITM002W Failure storing AOT code in shared class cache. Shared class cache might be corrupted. Ignoring AOT code in shared class cache.
Explanation
An error occurred storing AOT code in the shared class cache.System action
The compiler stops generating AOT code. AOT code from the shared class cache is not used.User response
Destroy and re-create the AOT code in the shared class cache using the -Xshareclasses:reset option.JVMJITM003W Failure during AOT runtime initialization. Ignoring AOT code in shared class cache.
Explanation
An error occurred initializing AOT.System action
The compiler does not generate AOT code. AOT code from the shared class cache is not used.User response
If the error occurs again, destroy and re-create the AOT code in the shared class cache using the -Xshareclasses:reset option.JVMJITM004W AOT code in shared class cache cannot execute on current processor. Ignoring AOT code in shared class cache.
Explanation
The AOT code in the shared class cache is not compiled for this platform.System action
The compiler does not generate AOT code. AOT code from the shared class cache is not used.User response
Destroy and re-create the AOT code in the shared class cache for the current platform using the -Xshareclasses:reset option.JVMJITM005W AOT code in the shared class cache cannot run on current JVM release. Ignoring AOT code in shared class cache.
Explanation
The AOT code in the shared class cache was created using a different JVM release.System action
The compiler does not generate AOT code. AOT code from the shared class cache is not used.User response
Destroy and re-create the AOT code in the shared class cache for the current JVM release using the -Xshareclasses:reset option.JVMJITM006W AOT code in shared class cache cannot run with current garbage collection policy. Ignoring AOT code in shared class cache.
Explanation
The AOT code in the shared class cache was created using a different garbage collection policy.System action
The compiler does not generate AOT code. AOT code from the shared class cache is not used.User response
Destroy and re-create the AOT code in the shared class cache for the current garbage collection policy using the -Xshareclasses:reset option.JVMJITM007W AOT code in shared class cache cannot run with current JVMPI or JVMTI settings. Ignoring AOT code in shared class cache.
Explanation
AOT code cannot be used with JVMPI or JVMTI.System action
The compiler does not generate AOT code. AOT code from the shared class cache is not used.User response
To use AOT code, disable JVMTI. JVMPI is replaced by JVMTI in Java 6.JVMJITM009E System configuration does not support parameter '%.*s' in option '-Xlp'
Explanation
The specified parameter is not recognized for the -Xlp option.System action
The JVM ends.User response
Remove the unrecognized parameter from the -Xlp option and try again.JVMJITM010E %s must be followed by a number
Explanation
The specified option must be followed immediately by a number.System action
The JVM ends.User response
Adjust the JIT option. For example, replace-Xlp:objectheap:pagesize <size> with -Xlp:objectheap:pagesize<size>.