The following table describes the list of the JavaVM extension options.
You can specify the following options in the option definition file. VR is the version of Application Server on which parameters are introduced or changed.
Related information is the reference location for information related to the specified key. uCosminexus Application Server is omitted from the manual names.
Table 16-1 List of JavaVM extension options
Classification | Option name | Overview | VR | Related information |
---|---|---|---|---|
List display option | -XX:+Hitachi | Display the list of JavaVM extension options. | Solaris version: 06-50 Others: version 05-02 | |
Extended thread dump functionality option | -XX:[+|-]HitachiThreadDump | Specify whether to output the extended thread dump information. | Windows version: 05-05 Solaris version: 06-50 Others: version 05-00 | |
-XX:[+|-]HitachiThreadDumpToStdout | Specify whether to output the thread dump as the standard output. | HP-UX/PA version: 06-70 Windows/IPF version: 06-70 Others: version 06-50 | ||
-XX:[+|-]HitachiThreadDumpWithHashCode | Specify whether to output the hash code in the thread information. | 07-00 | ||
-XX:[+|-]HitachiThreadDumpWithCpuTime | Specify whether to output the user CPU time and the kernel CPU time in the thread information. You cannot use this functionality in HP-UX. Even if you specify this option, it will be ignored. | 07-00 | ||
-XX:[+|-]HitachiThreadDumpWithBlockCount | Specify whether to output the number of times the process is blocked and the number of times the process is in the waiting status, in the thread information. | 07-00 | ||
JavaVM log file option | -XX:HitachiJavaLog#1 | Specify the prefix of log file name. | Solaris version: 06-50 Others: version 05-02 | |
-XX:HitachiJavaLogFileSize#1 | Specify the maximum file size of one file. | Solaris version: 06-50 Others: version 05-02 | ||
-XX:[+|-]HitachiJavaLogNoMoreOutput#1 | Specify the operation when the input/ output error occurs while creating a log file. | Solaris version: 06-50 Others: version 05-02 | ||
-XX:HitachiJavaLogNumberOfFile#1 | Specify the maximum number of log files to be created. | Solaris version: 06-50 Others: version 05-02 | ||
Detailed time output option | -XX:[+|-]HitachiOutputMilliTime | Specify whether to output the time up to milliseconds. | Solaris version: 06-50 HP-UX/PA version: 06-70 Others: 06-00 | |
Extended verbosegc functionality option | -XX:[+|-]HitachiVerboseGC#2 | Specify whether to output the extended verbosegc information when garbage collection occurs. | Solaris version: 06-50 Others: version 05-02 | |
-XX:[+|-]HitachiCommaVerboseGC | Specify whether to output the extended verbosegc information in CSV format. | Solaris version: 06-50 Others: version 05-02 | ||
-XX:HitachiVerboseGCIntervalTime | Specify the time interval in which the extended verbosegc information is to be output. | Solaris version: 06-50 Others: version 05-02 | ||
-XX:[+|-]HitachiVerboseGCPrintCause | Specify whether to output the cause of the garbage collection. | Solaris version: 06-50 Others: version 05-02 | ||
-XX:[+|-]HitachiVerboseGCPrintDate | Specify whether to output the date in the extended verbosegc information. | Solaris version: 06-50 Others: version 05-02 | ||
-XX:[+|-]HitachiVerboseGCCpuTime | Specify whether to output the processor time of the garbage collection. You cannot use this functionality in HP-UX. Even if you specify this option, it will be ignored. | 07-00 | ||
-XX:[+|-]HitachiVerboseGCPrintTenuringDistribution | Output the age distribution of objects in the Survivor area into the JavaVM log file, when garbage collection occurs. | 08-00 | ||
-XX:[+|-]HitachiVerboseGCPrintJVMInternalMemory | Specifies whether to output the heap information being managed in JavaVM to the JavaVM log file. | 08-53 | ||
-XX:[+|-]HitachiVerboseGCPrintThreadCount | Specifies whether to output the number of Java threads to the JavaVM log file in order to monitor the number of Java threads. | Linux version (x86/AMD64 & Intel EM64T): 08-53 Windows version x86: 08-53 Windows version x64: 08-53 Windows version x86 (for JDK 6 base): 08-70 | ||
-XX:[+|-]HitachiVerboseGCPrintDeleteOnExit | Specifies whether to output the cumulative heap size that JavaVM allocates by invoking the java.io.File.deleteOnExit() method and the method invocation count to the JavaVM log file. | Linux version (x86/AMD64 & Intel EM64T): 08-53 Windows version x86: 08-53 Windows version x64: 08-53 Windows version x86 (for JDK 6 base): 08-70 | ||
Options of the functionality to output the code cache area information | -XX:[+|-]PrintCodeCacheInfo | Specify whether to output the amount of code cache area used, and whether to output a message informing the user that the usage has reached the threshold value. | 09-50 | |
-XX:CodeCacheInfoPrintRatio | Specify the usage rate of the code cache area that will trigger the output of a message informing the user that the usage of the code cache area has reached the threshold value. | 09-50 | ||
-XX:[+|-]PrintCodeCacheFullMessage | Specify whether to output a message if the code cache area is depleted when the Java method is subject to JIT compilation. | 09-50 | ||
Extended functionality option when OutOfMemoryError occurs | -XX:[+|-]HitachiOutOfMemoryCause#2 | Specify whether to output the types of causes for the occurrence of OutOfMemoryError. | Solaris version: 06-50 Others: version 05-02 | |
-XX:[+|-]HitachiOutOfMemoryStackTrace#2 | Specify whether to output the stack trace when OutOfMemoryError occurs. | Solaris version: 06-50 Others: version 05-02 | ||
-XX:HitachiOutOfMemoryStackTraceLineSize | Specify the number of characters in one line of stack trace that is output when OutOfMemoryError occurs. | Solaris version: 06-50 Others: version 05-02 | ||
-XX:[+|-]HitachiOutOfMemorySize#2 | Output the requested memory size when OutOfMemoryError occurs. | HP-UX/PA version: 06-70 Windows/IPF version: 06-70 Others: version 06-50 | ||
-XX:[+|-]HitachiOutOfMemoryAbort | Specify whether to output the message and memory dump and perform the forced termination when OutOfMemoryError occurs. | HP-UX/PA version: 06-70 Windows/IPF version: 06-70 Others: version 06-50 | ||
-XX:[+|-]HitachiOutOfMemoryAbortThreadDump | Specify whether to output the thread dump when OutOfMemoryError occurs. | HP-UX/PA version: 06-70 Windows/IPF version: 06-70 Others: version 06-50 | ||
-XX:[+|-]HitachiOutOfMemoryAbortThreadDumpWithJHeapProf | Outputs class-wise statistical information to the thread dump log file output by -XX:+HitachiOutOfMemoryAbortThreadDump. | 08-00 | ||
-XX:[+|-]HitachiOutOfMemoryHandling | Specifies whether to enable the OutOfMemory handling functionality. | 08-53 | ||
-XX:HitachiOutOfMemoryHandlingMaxThrowCount | Specifies the per-hour upper limit for the total OutOfMemory occurrence count caused by a Java heap or Perm heap shortage when the OutOfMemory handling functionality is enabled. | 08-53 | ||
Class library trace functionality option | -XX:[+|-]HitachiJavaClassLibTrace#2 | Specify whether to output stack trace of the class library. | HP-UX/PA version: 06-70 Windows/IPF version: 06-70 Others: version 06-50 | |
-XX:HitachiJavaClassLibTraceLineSize | Specify the number of characters in one line of stack trace of the class library. | HP-UX/PA version: 06-70 Windows/IPF version: 06-70 Others: version 06-50 | ||
Local variable information output functionality option | -XX:[+|-]HitachiLocalsInThrowable | Specify whether to output the local variable information in the stack trace when exception occurs. | HP-UX/PA version: 06-70 Windows/IPF version: 06-70 Others: version 06-50 | |
-XX:[+|-]HitachiLocalsInStackTrace | Specify whether to output the local variable information in the stack trace when the thread dump is output. | HP-UX/PA version: 06-70 Windows/IPF version: 06-70 Others: version 06-50 | ||
-XX:[+|-]HitachiLocalsSimpleFormat | Specify whether to output the local variable information in simple format. | HP-UX/PA version: 06-70 Windows/IPF version: 06-70 Others: version 06-50 | ||
-XX:[+|-]HitachiTrueTypeInLocals | Specify a character string for whether you need to output the true type name of the local variable object when the local variable information is output. | HP-UX/PA version: 06-70 Windows/IPF version: 06-70 Others: version 06-50 | ||
-XX:HitachiCallToString | Specify a character string for whether you need to output the variable value of the local variable object when the local variable information is output. | HP-UX/PA version: 06-70 Windows/IPF version: 06-70 Others: version 06-50 | ||
Release system resource option | -XX:[+|-]HitachiFullCore | Specify whether to change the settings of the system resource RLIMIT_CORE. This option is for UNIX. | Solaris version: 06-50 Others: version 05-02 | |
Reserve swap area option | -XX:[+|-]HitachiReserveSwapSpace | Specify whether to reserve the maximum swap area required to run JavaVM, when starting JavaVM. This option is used for HP-UX. | HP-UX/PA version: 06-70 HP-UX/IPF version: version 06-00 | |
Options specified in the explicit memory management | -XX:[+|-]HitachiUseExplicitMemory | Specify whether to enable or disable the Explicit Memory Management function. | 08-00 | |
-XX:HitachiExplicitHeapMaxSize | Specify the maximum size of the entire Explicit heap. | 08-00 | ||
-XX:HitachiExplicitMemoryLogLevel | Specify the event log level of the Explicit Memory Management functionality. | 08-00 | ||
-XX:HitachiExplicitMemoryJavaLog | Specify the file name (path name can be included) or directory name in which the log will be output using this functionality. | 08-00 | ||
-XX:HitachiExplicitMemoryJavaLogFileSize | Set up the maximum file size of one file in bytes. | 08-00 | ||
-XX:HitachiExplicitMemoryJavaLogNumberOfFile | Specify the maximum number of files to be created. If the maximum number of files is exceeded, the log is output again to the file that was created first (wrap around). | 08-00 | ||
-XX:[+|-]HitachiExplicitMemoryMoveToTenuredFirst | Specify the transition destination of the objects of the release process of Explicit memory block. | 08-50 | 8. Controlling Full Garbage Collection Using the Explicit Memory Management functionality in Expansion Guide | |
-XX:[+|-]HitachiExplicitMemoryAutoReclaim | Specify whether to enable the automatic release function of the Explicit Memory Management functionality. | 08-50 | ||
Version compatibility option of the Explicit Memory Management function | -XX:[+|-]HitachiExplicitMemoryCompatibleToV8 | Specify whether to use the same method as in 08-00 for securing the Explicit memory block. | 08-50 | |
Options in the Explicit Memory Management automatic allocation setup file | -XX:[+|-]HitachiAutoExplicitMemory | Specify whether to enable the automatic allocation function for the Explicit memory block. | 08-50 | |
-XX:HitachiAutoExplicitMemoryFile | Specify the path of the automatic allocation setup file to be used by the automatic allocation function of the Explicit memory block. | 08-50 | ||
Option for controlling the transfer of objects to the Explicit memory block of the Explicit Memory Management functionality | -XX:ExplicitMemoryFullGCPolicy | Specify whether to control the transfer of reference relationship-based objects from the Java heap to the Explicit memory block when a full garbage collection occurs. | 09-50 | 8. Controlling Full Garbage Collection Using the Explicit Memory Management functionality in Expansion Guide |
Option for the functionality for specifying the classes to be excluded from the Explicit Memory Management functionality | -XX:[+|-]ExplicitMemoryUseExcludeClass | Specify whether to enable the functionality for specifying the classes to be excluded from the Explicit Memory Management functionality. | 09-50 | |
-XX:ExplicitMemoryExcludeClassListFile | Specify the path of the Explicit Memory Management functionality exclusion setup file to be used with the functionality for specifying the classes to be excluded from the Explicit Memory Management functionality. | 09-50 | ||
-XX:ExplicitMemoryNotExcludeClassListFile | Specify the path of the Explicit Memory Management functionality non-exclusion setup file to be used with the functionality for specifying the classes to be excluded from the Explicit Memory Management functionality. | 09-50 | ||
Memory usage reduction option for the Explicit heap used in an HTTP session | -XX:[+|-]HitachiExplicitMemoryAutoRefReclaim | Specifies whether to enable the memory usage reduction function for the Explicit heap used in an HTTP session. | 08-70 | 8. Controlling Full Garbage Collection Using the Explicit Memory Management functionality in Expansion Guide |
Option for specifying the maximum resources | -XX:HitachiJITCompileMaxMemorySize | Specifies the upper limit of the memory to be secured for the JIT compilation. | 08-53 | |
-XX:HitachiThreadLimit | Specifies the upper limit for the number of threads. | 08-53 | ||
Option for the JIT compiler continuation functionality | -XX:[+|-]JITCompilerContinuation | Specify whether to enable the JIT compiler continuation functionality. | 09-50 |
Table 16-2 References for the default values of JavaVM extension options for each server and application
Server and application used | Reference |
---|---|
J2EE server | 2.3 usrconf.cfg (Option definition file for J2EE servers) |
Batch server | 3.2 usrconf.cfg (Option definition file for batch servers) |
Web container server (compatibility function) | 3.11.2 usrconf.cfg (Option definition file for Web container server) in the manual Cosminexus Application Server Function Guide - Compatibility |
Java applications started with the cjclstartap command | 14.2 usrconf.cfg (Option definition file for Java applications) |
Other Java applications | 16.4 Default values of the Java HotSpot VM options that can be specified in Cosminexus |