Bug 1213248

Summary:	VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 - unsupported JVM property
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Miroslav Novak <mnovak>
Component:	Scripts and Commands	Assignee:	Tomaz Cerar <tcerar>
Status:	CLOSED DUPLICATE	QA Contact:	Marek Kopecky <mkopecky>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.4.0	CC:	fnasser, pgier, pkremens
Target Milestone:	---
Target Release:	EAP 6.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-04-20 12:28:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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