"Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0" message is send on standard error output when EAP 6.3.0 is started using JDK8.
PermGen was removed in JDK8, our scripts should reflect it.
We should suppress message on standard error output when running EAP.
There is no nice way for doing this.
We would need to update all scripts with few ugly hacks executing java -version to see what kind of version it is and than based on that modify parameters.
Beyond that we would need to change domain.xml/host.xml configs.
I think the best thing we can do is actually ignore <permgen> settings for host/domain in case of JDK8.
In any case I don't see any big need for it, especially since JDK8 is just one of JDKs we support.
This is an RFE. The VM settings we ship in the user-updatable .conf files are suggestions to get users started, they aren't something we say will work flawlessly in all cases. If the settings are unsuitable for a user's environment they should change them.
I was looking into actual problems related to this when trying to run WildFly on JDK9.
In JDK8 we get a warning, with JDK9 on the other hand jvm doesn't start if premgen parameter is set.
This will address this as part of ongoing effort for running upstream WildFly on JDK9 but this is really low priority as JDK9 is still in early dev phase.
*** Bug 1213248 has been marked as a duplicate of this bug. ***
Tomaz Cerar <email@example.com> updated the status of jira WFLY-3854 to Reopened