-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
1.0.0.Beta5
- If the "host.xml" has the following JVM name defined
<jvms> <jvm name="default"> <heap size="200m" max-size="2000m"/> <permgen size="256m" max-size="256m"/> <jvm-options> <option value="-server"/> </jvm-options> </jvm> <jvm name="Test"> <heap size="300m" max-size="2500m"/> <permgen size="128m" max-size="128m"/> </jvm> </jvms>
- If the server refers to the above JVM name as following:
<servers> <server name="server-one" group="main-server-group" auto-start="true"> <jvm name="Test"/> </server> </servers>
- In above case when the server-one is booted that time it takes the value from "server-group" (in this case main-server-group) defined in the domain.xml
<server-groups> <server-group name="main-server-group" profile="full"> <jvm name="default"> <heap size="64m" max-size="512m"/> </jvm>
So the JVM settings defined for JVM name "Test" is overridden by server-group values:
30201 jboss-modules.jar -agentpath:/usr/lib64/libabrt-java-connector.so=abrt=on -D[Server:server-one] -XX:PermSize=128m -XX:MaxPermSize=128m -Xms64m -Xmx512m -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Djboss.home.dir=/wildfly-9.0.0.CR1-SNAPSHOT -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.server.log.dir=/wildfly-9.0.0.CR1-SNAPSHOT/domain/servers/server-one/log -Djboss.server.temp.dir=/wildfly-9.0.0.CR1-SNAPSHOT/domain/servers/server-one/tmp -Djboss.server.data.dir=/wildfly-9.0.0.CR1-SNAPSHOT/domain/servers/server-one/data -Dlogging.configuration=file:/wildfly-9.0.0.CR1-SNAPSHOT/domain/servers/server-one/data/logging.properties
NOTICE the JVM runtime value is -Xms64m -Xmx512m, where as it was supposed to be -Xms300m -Xmx2500m as that is the "Test" jvm setting.
- is related to
-
HAL-642 Console does not allow adding existing jvm name to the server in domain mode.
- Resolved