[
https://issues.jboss.org/browse/JBDS-4386?page=com.atlassian.jira.plugin....
]
Rob Stryker commented on JBDS-4386:
-----------------------------------
Running eap 6.4 from cmd line:
{code}
[rob@rawbdorable bin]$ ./standalone.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /home/rob/apps/jboss/unzipped/jboss-eap-6.4.0.zip.expanded
JAVA: /home/rob/apps/java/java8/jdk1.8.0_05//bin/java
JAVA_OPTS: -server -XX:+UseCompressedOops -verbose:gc
-Xloggc:"/home/rob/apps/jboss/unzipped/jboss-eap-6.4.0.zip.expanded/standalone/log/gc.log"
-XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -Xms1303m -Xmx1303m
-XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
-Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
-Djboss.modules.policy-permissions=true
=========================================================================
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was
removed in 8.0
{code}
I can obviously make changes, but I'd rather not diverge from the command line, and
due to the nature of the way the subclasses extend each other, I'd rather not fix it
here.
I will look into fixing eap 7.x / wf11 here if it occurs there. But I won't fix it for
eap 6.x
Please correct launch configuration so WARN is no longer provided by
default
----------------------------------------------------------------------------
Key: JBDS-4386
URL:
https://issues.jboss.org/browse/JBDS-4386
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: common
Affects Versions: 10.3.0.GA
Environment: DevStudio 10.3, as used with an EAP server.
Reporter: Rick Wagner
Assignee: Rob Stryker
Priority: Minor
Fix For: 11.0.0.AM1
Using default settings, an EAP 6.4 (Fuse) server gives the following WARN in the Console
view:
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was
removed in 8.0
Removal of the following param from VM arguments resolves the issue:
-XX:MaxPermSize=256m
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)