[jbosstools-issues] [JBoss JIRA] (JBIDE-20591) Don't set default MaxPermSize for EAP 7/WF 10 launch configs
Rob Stryker (JIRA)
issues at jboss.org
Tue Sep 8 15:50:00 EDT 2015
[ https://issues.jboss.org/browse/JBIDE-20591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Stryker resolved JBIDE-20591.
---------------------------------
Assignee: Rob Stryker
Resolution: Done
Pushed to master for cr1
> Don't set default MaxPermSize for EAP 7/WF 10 launch configs
> ------------------------------------------------------------
>
> Key: JBIDE-20591
> URL: https://issues.jboss.org/browse/JBIDE-20591
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.CR1
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.x
>
>
> WildFly 10 and EAP 7 require Java 8 to run. When any of these server is created, the launch configuration is set with -XX:MaxPermSize=256m, which results in a warning being displayed in the console:
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
> Since we guarantee that Java 8 minimum will run, the MaxPermSize arg should be removed from default launch configurations for these 2 servers.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list