blocks|key|2962175|text|Compatibility+Guide+for+JDK+8说，在Java8中，命令行标志MaxPermSize已被删除。原因是永久生成已从热点堆中删除，并移至本机内存。因此，要删除此消息，请编辑MAVEN_OPTS环境用户变量：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|BOLD|entityRanges|data|2962176|Java+7|2962177|MAVEN_OPTS+-Xmx512m+-XX:MaxPermSize=128m|code-block|syntax|javascript|2962178|Java+8|2962179|MAVEN_OPTS+-Xmx512m|2962180|entityMap|0|LINK|mutability|MUTABLE|url|http://www.oracle.com/technetwork/java/javase/8-compatibility-guide-2156366.html^0|18|B|2P|A|0|T|0|0|0|6|0|0|0|6|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|D]]|E|@$9|14|A|15|1|16]]|F|$]]|$1|G|3|H|5|6|7|17|8|@$9|18|A|19|B|D]]|E|@]|F|$]]|$1|I|3|J|5|K|7|1A|8|@]|E|@]|F|$L|M]]|$1|N|3|O|5|6|7|1B|8|@$9|1C|A|1D|B|D]]|E|@]|F|$]]|$1|P|3|Q|5|K|7|1E|8|@]|E|@]|F|$L|M]]|$1|R|3|-4|5|6|7|1F|8|@]|E|@]|F|$]]]|S|$T|$5|U|V|W|F|$X|Y]]]]

<a href="http://www.oracle.com/technetwork/java/javase/8-compatibility-guide-2156366.html">Compatibility Guide for JDK 8</a> says that in Java 8 the command line flag <code>MaxPermSize</code> 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

<pre><code>MAVEN_OPTS -Xmx512m -XX:MaxPermSize=128m
</code></pre>

Java 8

<pre><code>MAVEN_OPTS -Xmx512m
</code></pre>

blocks|key|157607|text|JDK8MetspaceJVM现在使用本机内存来表示类元数据，并被称为+HotSpot+。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|157608|永久一代已被删除。如果命令行中存在PermSize和MaxPermSize，则会忽略它们并发出警告。|CODE|157609|entityMap^0|0|F|Z|9|0|H|8|Q|B|0^^$0|@$1|2|3|4|5|6|7|K|8|@$9|L|A|M|B|C]|$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|P|8|@$9|Q|A|R|B|H]|$9|S|A|T|B|H]]|D|@]|E|$]]|$1|I|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|J|$]]

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 <code>PermSize</code> and <code>MaxPermSize</code> are ignored and a warning is issued if they are present on the command line.

blocks|key|160080|text|在JBoss+EAP6.4中，右键单击服务器并打开VM参数下的启动配置，您将看到|type|unstyled|depth|inlineStyleRanges|entityRanges|data|160081|{-Dprogram.name=JBossTools:+jboss-eap"+-server+-Xms1024m+-Xmx1024m+-XX:MaxPermSize=256m}|code-block|syntax|javascript|160082|将其更新为|160083|{-Dprogram.name=JBossTools:+JBoss+6.4"+-server+-Xms512m+-Xmx512m}|160084|这将解决您的问题。|160085|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

In JBoss EAP 6.4, right click on the server and open launch configuration under VM argument you will find 

<pre><code>{-Dprogram.name=JBossTools: jboss-eap" -server -Xms1024m -Xmx1024m -XX:MaxPermSize=256m}
</code></pre>

update it to

<pre><code>{-Dprogram.name=JBossTools: JBoss 6.4" -server -Xms512m -Xmx512m}
</code></pre>

this will solve your problem.

blocks|key|158919|text|-XX:MaxPermSize=size|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|158920|设置永久生成空间的最大大小(字节)。该选项在JDK8中已被弃用，并被-XX:MaxMetaspaceSize选项取代。|unstyled|offset|length|style|CODE|158921|-XX:PermSize=size|158922|设置分配给永久生成的空间(以字节为单位)，如果超出永久生成，将触发垃圾回收。此选项在JDK8中已被弃用，并被-XX:MetaspaceSize选项取代。|BOLD|158923|entityMap^0|0|Y|K|0|0|16|4|1I|H|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|S|8|@$G|T|H|U|I|J]]|9|@]|A|$]]|$1|K|3|L|5|6|7|V|8|@]|9|@]|A|$B|C]]|$1|M|3|N|5|F|7|W|8|@$G|X|H|Y|I|O]|$G|Z|H|10|I|J]]|9|@]|A|$]]|$1|P|3|-4|5|F|7|11|8|@]|9|@]|A|$]]]|Q|$]]

<pre><code>-XX:MaxPermSize=size
</code></pre>

Sets the maximum permanent generation space size (in bytes). This option was deprecated in JDK 8, and superseded by the <code>-XX:MaxMetaspaceSize</code> option.

<pre><code>-XX:PermSize=size
</code></pre>

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 <code>-XX:MetaspaceSize</code> option.

blocks|key|2962388|text|在使用Java+8的Linux上运行命令行mvn+(版本3.3.3)时，我收到了类似的消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2962389|MAVEN_OPTS="$(concat_lines+"$MAVEN_PROJECTBASEDIR/.mvn/jvm.config")+$MAVEN_OPTS"|code-block|syntax|javascript|2962390|其中，默认情况下，$MAVEN_PROJECTBASEDIR是您的主目录。因此，您可以查看两个地方，首先是文件$MAVEN_PROJECTBASEDIR/.mvn/jvm.config+(如果存在)。其次，查看可能设置环境变量MAVEN_OPTS的文件。候选文件是.bashrc、.bash_profile、.profile及其包含的文件，例如/etc/profile、/etc/bash.bashrc|2962391|我找到了|2962392|export+MAVEN_OPTS="-Xmx512m+-XX:MaxPermSize=256m"|2962393|在我的系统的.bashrc中，将其更改为|2962394|export+MAVEN_OPTS="-Xmx512m"|2962395|问题已解决|2962396|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|Y|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

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

<pre><code>MAVEN_OPTS="$(concat_lines "$MAVEN_PROJECTBASEDIR/.mvn/jvm.config") $MAVEN_OPTS"
</code></pre>

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

<pre><code>export MAVEN_OPTS="-Xmx512m -XX:MaxPermSize=256m"
</code></pre>

in .bashrc in my system, change it to

<pre><code>export MAVEN_OPTS="-Xmx512m"
</code></pre>

issue resolved

blocks|key|161381|text|为了解决这个问题，我们刚刚在中设置了安装JDK路径|type|unstyled|depth|inlineStyleRanges|entityRanges|data|161382|161383|+standalone.conf|blockquote|161384|161385|161386|该文件位于JBoss\Wildfly+Server的bin文件夹下。为了解决这个问题，我们执行以下步骤：|offset|length|style|BOLD|161387|打开standlone.conf文件，该文件在此文件中的|161388|文件夹下找到#JAVA_HOME+text。|unordered-list-item|161389|
|161390|删除#字符并将已安装的JDK路径设置为JAVA_HOME="C:\Program+Files\Java\jdk1.8.0_65"希望这将解决您的问题谢谢|161391|161392|entityMap^0|0|0|0|0|0|Q|3|0|2|E|0|6|A|0|0|2|1|J|19|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|11|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|14|8|@$J|15|K|16|L|M]]|9|@]|A|$]]|$1|N|3|O|5|6|7|17|8|@$J|18|K|19|L|M]]|9|@]|A|$]]|$1|P|3|Q|5|R|7|1A|8|@$J|1B|K|1C|L|M]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1D|8|@]|9|@]|A|$]]|$1|U|3|V|5|R|7|1E|8|@$J|1F|K|1G|L|M]|$J|1H|K|1I|L|M]]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|Y|$]]

Please to solve this problem we just have set installed JDK path in 

<blockquote>
 standalone.conf
</blockquote>

file which under the bin folder of JBoss\Wildfly Server. To solve this we do the following steps:

<ol>
<li>Open the standlone.conf file which under JBoss_or_wildfly\bin folder</li>
<li>Within this file find for #JAVA_HOME text. </li>
<li>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</li>
</ol>

blocks|key|161397|text|对于Eclipse用户...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|161398|单击Run+->+Run+configuration+->+are+->+set+Alternate+JRE+for+1.6+or+1.7|161399|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

For Eclipse users...

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

blocks|key|2962478|text|以防有人仍然收到这样的信息。这是因为您在运行maven项目时添加了JVM参数。因为它与maven相关，所以您可以在项目中检查pom.xml文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2962479|找到这一行<argLine>...</argLine>，在我的项目上我也有下面的论点|2962480|<argLine>-Xmx1024m+-XX:MaxPermSize=512m+-XX:%2BTieredCompilation+-XX:TieredStopAtLevel=1</argLine>|code-block|syntax|javascript|2962481|您应该将MaxPermSize参数替换为-Xms123m+-Xmx123m，因为MaxPermSize已经被弃用，并且不会对您的JVM配置产生任何影响：|2962482|<argLine>-Xms512m+-Xmx512m++-XX:%2BTieredCompilation+-XX:TieredStopAtLevel=1</argLine>|2962483|entityMap^0|1Q|7|0|5|M|0|0|4|B|K|H|14|B|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@]|E|$]]|$1|O|3|P|5|J|7|16|8|@]|D|@]|E|$K|L]]|$1|Q|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|R|$]]

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 <code>pom.xml</code> file on your project.

find this line <code>&lt;argLine&gt;...&lt;/argLine&gt;</code>, on my project I also have argument below 

<pre><code>&lt;argLine&gt;-Xmx1024m -XX:MaxPermSize=512m -XX:+TieredCompilation -XX:TieredStopAtLevel=1&lt;/argLine&gt;
</code></pre>

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

<pre><code>&lt;argLine&gt;-Xms512m -Xmx512m -XX:+TieredCompilation -XX:TieredStopAtLevel=1&lt;/argLine&gt;
</code></pre>

When building a Java 8 project with Maven:

<pre><code>mvn clean package
</code></pre>

I get this message:

<blockquote>
 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
</blockquote>

How to remove this message?

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

服务器

Eclipse

Linux

Java

在使用Maven构建Java 8项目时：mvn clean package我得到了这样的信息： Java HotSpot(TM) 64位服务器VM警告:忽略选项MaxPermSize=128m；8.0中删除了对该选项的支持如何删除此消息？

问Java HotSpot(TM) 64位服务器VM警告:忽略选项MaxPermSize
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Java HotSpot(TM) 64位服务器VM警告:忽略选项MaxPermSizeEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Java HotSpot(TM) 64位服务器VM警告:忽略选项MaxPermSize
EN