-XX:ExplicitMemoryNotExcludeClassListFile (Option for specifying the path of the Explicit Memory Management functionality non-exclusion setup file)
- Organization of this page
Format
-XX:ExplicitMemoryNotExcludeClassListFile:character-string
Description
Specify the file path of the Explicit Memory Management functionality non-exclusion setup file used with the functionality for specifying the classes to be excluded from the Explicit Memory Management functionality. The functionality for specifying the classes to be excluded from the Explicit Memory Management functionality is not applied to the classes coded in this file even if the classes are also coded in the Explicit Memory Management functionality exclusion setup file.
When JavaVM starts, the file in the file path specified in this option is read as the Explicit Memory Management functionality non-exclusion setup file. Note that if you omit this option or specify null, the file in the default file path will be read as the Explicit Memory Management functionality non-exclusion setup file.
- Default value
-
-
-XX:ExplicitMemoryNotExcludeClassListFile:Null
- In Windows
-
JDK-installation-directory\usrconf\exmemnotexcludeclass.cfg
- In UNIX
-
/opt/Cosminexus/jdk/usrconf/exmemnotexcludeclass.cfg
-
- Prerequisite options
-
-
-XX:+HitachiUseExplicitMemory
-
-XX:+ExplicitMemoryUseExcludeClass
-
- Related options
-
-
-XX:ExplicitMemoryFullGCPolicy
-
-XX:HitachiAutoExplicitMemory
-
-XX:ExplicitMemoryExcludeClassListFile
-
Argument
- character-string
-
Specify the relative path from the current directory of the JavaVM process, or the absolute path. You can include the directory name in the path.
Note that you can only specify one Explicit Memory Management functionality exclusion setup file. Also, use the ASCII code for the character encoding in the file.
Notes
-
If the specified file cannot be opened or read, a warning message will be output to the event log of the Explicit Memory Management functionality, and the setup file in the default path will be read. If the file in the default path cannot be opened or read, the functionality for specifying the classes to be excluded from the Explicit Memory Management functionality will not be disabled.
-
If the coding format of the specified file is incorrect, a warning message will be output to the event log of the Explicit Memory Management functionality and the syntax analysis continues from the next line.
-
If the same class names are coded in both the Explicit Memory Management functionality exclusion setup file and the Explicit Memory Management functionality non-exclusion setup file, the specification in the Explicit Memory Management functionality non-exclusion setup file is given priority. In this case, the functionality for specifying the classes to be excluded from the Explicit Memory Management functionality will be disabled for those classes.