How to avoid message "Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0" in Wildfly 8.2?

claudinei Dec 11, 2014 6:47 AM

When I start WildFly 8.2 this shows in console: "Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0" the only way i found to avoid this is comment the above lines in bin/standalone.conf:

#if [ "x$JAVA_OPTS" = "x" ]; then
#   JAVA_OPTS="-Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true"
#   JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
#else
#   echo "JAVA_OPTS already set in environment; overriding default settings with values: $JAVA_OPTS"
#fi

There is a better way to do this?

Thanks.

1. Re: How to avoid message "Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0" in Wildfly 8.2?

ctomc Dec 11, 2014 7:11 AM (in response to claudinei)

That is the right way.

Only other way would be to set $JAVA_OPTS as env variable before starting the server.

something along the lines:
export JAVA_HOME="-Xms64m -Xmx512m -Djava.net.preferIPv4Stack=true -Djava.awt.headless=true"
./standalone.sh

but editing standalone.conf is perfectly fine and expected. as that values there are just default that should be changed to match your running environment.

Defaults are set in a way that makes sure that server starts on as many different JVM/OS-es as possible. And are not optimized for one or another os/jvm.

And, don't just comment out the whole JAVA_OPTS line as you might run into problems, just remove the -XX:MaxPermSize=256m parameter.
Actions