Salesforce

JDK 8 warning PermSize and MaxPermSize JVM arguments are ignored

« Go Back

Information

 
TitleJDK 8 warning PermSize and MaxPermSize JVM arguments are ignored
URL NameJDK-8-warning-PermSize-and-MaxPermSize-JVM-arguments-are-ignored
Article Number000168901
EnvironmentProduct : OpenEdge
Version: 11.6x, 11.7x
OS : All supported platforms
Question/Problem Description
When a Java 8 process is started, the following warnings are thrown:
Java HotSpot(TM) Server VM warning: ignoring option PermSize=<number>m support was removed in 8.0
Java HotSpot(TM) Server VM warning: ignoring option MaxPermSize=<number>m support was removed in 8.0
Steps to Reproduce
Clarifying Information
Error MessageJava HotSpot(TM) Server VM warning: ignoring option PermSize=<number>m support was removed in 8.0
Java HotSpot(TM) Server VM warning: ignoring option MaxPermSize=<number>m support was removed in 8.0
Defect Number
Enhancement Number
Cause
The PermGen successor in Java 8 uses native memory for the representation of class metadata and is called: Metaspace

The consequences of the PermGen removal is the PermSize and MaxPermSize JVM arguments are ignored and a warning is issued if present at start-up.
Resolution
By default the MetaSpace space limit is unbounded. Metaspace objects e.g. Class metadata waste are only collected during a Full GC event.
  • Remove -XX:PermSize and -XX:MaxPermSize from JVM arguments (jvmargs) in OpenEdge *.properties configuration files
  • Optionally, the maximum metaspace size can be set using the -XX:MaxMetaspaceSize flag to force the JVM into Full GC clean the Metadata/Reflection waste, preventing excessive consumption of physical/virtual memory. Restricting metaspace can result in java.lang.OutOfMemoryError: Metadata
Workaround
Notes
Keyword Phrase
Last Modified Date11/20/2020 7:05 AM

Powered by