Java HotSpot TM 64-Bit Server VM warning ignoring option MaxPermSize

Question

When building a Java 8 project with Maven   mvn clean package   I get this message      Java HotSpot TM  64-Bit Server VM warning  ignoring option MaxPermSize 128m  support was removed in 8 0   How to remove this message

User · Answer

in case some one still get this kind of message. Its happen because you add JVM argument when running maven project. Because it is related with maven you can check your pom.xml file on your project.

find this line <argLine>...</argLine>, on my project I also have argument below

<argLine>-Xmx1024m -XX:MaxPermSize=512m -XX:+TieredCompilation -XX:TieredStopAtLevel=1</argLine>

you should replace MaxPermSize argument as -Xms123m -Xmx123m, since MaxPermSize is already deprecated and wont take any effect on your JVM config :

<argLine>-Xms512m -Xmx512m  -XX:+TieredCompilation -XX:TieredStopAtLevel=1</argLine>

User · Answer

For Eclipse users     Click Run      Run configuration      are      set Alternate JRE for 1 6 or 1 7

User · Answer

Please to solve this problem we just have set installed JDK path in      standalone conf   file which under the bin folder of JBoss Wildfly Server  To solve this we do the following steps    Open the standlone conf file which under JBoss or wildfly bin folder Within this file find for  JAVA HOME text   Remove the   character and set your installed JDK path as  JAVA HOME  C  Program Files Java jdk1 8 0 65  Hope this will solve your problem Thanks

User · Answer

Compatibility Guide for JDK 8 says that in Java 8 the command line flag MaxPermSize has been removed  The reason is that the permanent generation was removed from the hotspot heap and was moved to native memory  So in order to remove this message edit MAVEN OPTS Environment User Variable   Java 7  MAVEN OPTS -Xmx512m -XX MaxPermSize 128m   Java 8  MAVEN OPTS -Xmx512m

User · Answer

In JBoss EAP 6 4  right click on the server and open launch configuration under VM argument you will find    -Dprogram name JBossTools  jboss-eap  -server -Xms1024m -Xmx1024m -XX MaxPermSize 256m    update it to   -Dprogram name JBossTools  JBoss 6 4  -server -Xms512m -Xmx512m    this will solve your problem

User · Answer

I got similar message when running command line mvn  version 3 3 3  on Linux with Java 8  By opening maven script   MAVEN-HOME bin mvn  found the following line  MAVEN OPTS    concat lines   MAVEN PROJECTBASEDIR  mvn jvm config    MAVEN OPTS    Where  MAVEN PROJECTBASEDIR by default is your home directory  So two places you can take a look  first is file  MAVEN PROJECTBASEDIR  mvn jvm config if it exists  Secondly look at files possibly set up the environment variable MAVEN OPTS  Candidate files are  bashrc   bash profile   profile and those files included by them such as  etc profile   etc bash bashrc  I located  export MAVEN OPTS  -Xmx512m -XX MaxPermSize 256m    in  bashrc in my system  change it to  export MAVEN OPTS  -Xmx512m    issue resolved

User · Answer

The JDK 8 HotSpot JVM is now using native memory for the representation of class metadata and is called Metaspace   The permanent generation has been removed  The PermSize and  MaxPermSize are ignored and a warning is issued if they are present on the command line

User · Answer

-XX MaxPermSize size   Sets the maximum permanent generation space size  in bytes   This option was deprecated in JDK 8  and superseded by the -XX MaxMetaspaceSize option   -XX PermSize size   Sets the space  in bytes  allocated to the permanent generation that triggers a garbage collection if it is exceeded  This option was deprecated in JDK 8  and superseded by the -XX MetaspaceSize option

[java] Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize

Examples related to java

Examples related to maven