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?

See http://bugs.java.com/bugdatabase/view_bug.do?bug_id=6964458 for a full description — Dag, Jun 25 '14 at 08:03
You may already have one instance of IDEA running. [1]: http://stackoverflow.com/a/20553943/3741698 — David Hackro, Jun 22 '15 at 03:14

Boris · Accepted Answer · 2014-03-25T13:05:21.050

174

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

edited Mar 25 '14 at 13:05

answered Mar 25 '14 at 12:30

Boris

22,667
16
50
71

14

And the reason is that the whole PermGen space has been removed in Oracle's JRE 8, AFAIK. – Puce Mar 25 '14 at 12:32
2

If someone does not know how to do this - `sudo gedit ~/.profile`, add the line from the answer there and save the file. – gotqn Jul 01 '15 at 13:16
I have this option set in ~/.bashrc file – paka Mar 10 '17 at 11:25
@gotqn Why would you `sudo` edit a file in your home folder? Seems like very strange practice to me. – Per Lundberg Apr 13 '18 at 16:16

score 22 · Answer 2 · edited Dec 21 '19 at 07:42

22

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.

edited Dec 21 '19 at 07:42

Yousha Aleayoub

4,532
4
53
64

answered Mar 25 '14 at 12:38

Martin Seeler

6,874
3
33
45

1

This only indirectly answers the question... The answer is "remove the flags to remove the warning". As the [insightful comment](https://stackoverflow.com/questions/22634644/java-hotspottm-64-bit-server-vm-warning-ignoring-option-maxpermsize#comment54226301_32365351) by @ohad-schneider reveals, there is no _one_ single replacement for them. – conny May 22 '20 at 05:18

score 13 · Answer 3 · edited Dec 21 '19 at 07:42

13

-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.

edited Dec 21 '19 at 07:42

Yousha Aleayoub

4,532
4
53
64

answered Sep 03 '15 at 00:50

mama...

149
1
2

17

I think this was downvoted because it implies that you should switch previous uses of `MaxPermGen` with `MaxMetaSpaceSize` which is misleading, since their roles have practically reversed. Before Java 8 class metadata space resided in PermGen which was limited by 32/64MB, and `MaxPerGen` was used to *increase* it. Starting from Java 8 however, PermGen is no more and class metadata space is unlimited, so `MaxMetaspace` size is actually used to *decrease* it. For more information see: http://stackoverflow.com/a/31463972/67824 – Ohad Schneider Oct 19 '15 at 09:32

score 8 · Answer 4 · edited Mar 20 '16 at 18:06

8

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.

edited Mar 20 '16 at 18:06

Ondra Žižka

43,948
41
217
277

answered Aug 21 '15 at 23:22

Amit

89
1
1

score 1 · Answer 5 · answered Dec 13 '15 at 01:52

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

adding this in .zshrc file resolved this issue: export MAVEN_OPTS="-Xmx512m" — Naga, Feb 19 '23 at 21:43

score 1 · Answer 6 · answered May 07 '20 at 06:52

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>

score -1 · Answer 7 · answered Oct 26 '16 at 05:03

-1

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

answered Oct 26 '16 at 05:03

Salahin Rocky

415
9
18

The original problem is in a maven project. It has nothing to do with JBoss. – Boris Oct 26 '16 at 15:45

score -5 · Answer 8 · answered Apr 06 '17 at 07:34

-5

For Eclipse users...

Click Run —> Run configuration —> are —> set Alternate JRE for 1.6 or 1.7

answered Apr 06 '17 at 07:34

Raja Rajamani

1
2

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

8 Answers8

Linked

Related