Bug 1213248 - VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 - unsupported JVM property
Summary: VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 - un...
Keywords:
Status: CLOSED DUPLICATE of bug 1081034
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Scripts and Commands
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: EAP 6.4.0
Assignee: Tomaz Cerar
QA Contact: Marek Kopecky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-20 07:10 UTC by Miroslav Novak
Modified: 2015-04-20 12:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-20 12:28:54 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Miroslav Novak 2015-04-20 07:10:45 UTC 
Description of problem:

If EAP 6.4.0 is started on with JDK 8 then JVM logs warning:

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0

This is because property MaxPermSize is not present in JVM 8. 

We set this property in JAVA_OPTS in standalone.conf and domain.conf:
   JAVA_OPTS="-Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true"

Expected results:

If possible, modify standalone/domain.conf in the was that this warning is not logged by JVM.
Comment 1 Tomaz Cerar 2015-04-20 12:28:54 UTC 
This is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1081034 and same comments still apply.
In short, there is no feasible way to make EAP work across JDK6, 7 and 8 with common set of jvm parameters.
Only downside is that on JDK8 you get warning as such.

*** This bug has been marked as a duplicate of bug 1081034 ***
Note You need to log in before you can comment on or make changes to this bug.