WildFly JVM Settings
Jump to navigation
Jump to search
Internal
Overview
JVM settings can be declared in various server configuration files, as shown below. In domain mode, these settings propagate to server node JVMs; the process controller and host controller JVM settings are declared in domain.conf.
Configuration
Standalone Mode
Modify standalone.conf as follows:
... JAVA_OPTS="-Xms1000m -Xmx2000m -XX:MetaspaceSize=256m -XX:MaxMetaspaceSize=512m ..." ...
Even if standalone*.xml allows for a <jvm> element, it seems it is not honored when specified. More research is needed on this.
Domain Mode
domain.xml
<domain ...> ... <server-groups> <server-group name="..."> <jvm java-home="..." type="SUN|IBM" env-classpath-ignored="true" debug-enabled="false" debug-options="..."> <heap size="" max-size=""/> <permgen>...</permgen> <stack>...</stack> <agent-lib>...</agent-lib> <agent-path>...</agent-path> <java-agent>...</java-agent> <jvm-options> <option name="...">....</option> ... </jvm-options> <environment-variables>...</environment-variables> <launch-command>...</launch-command> </jvm> </server-group> </server-groups> ... </server>
Example:
<jvm> <heap size="1000m" max-size="2000m"/> <jvm-options> <option value="-server"/> <option value="-XX:MetaspaceSize=256m"/> <option value="-XX:MaxMetaspaceSize=512m"/> </jvm-options> </jvm>
host.xml
host.xml allows "named" <jvm> declarations.
<host ..> ... <jvms> <jvm name="jvm-a" ...> </jvm name="jvm-b" ...> ... </jvms> ... </host>