WildFly and Garbage Collection Logging: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 41: Line 41:
</jvm-options>
</jvm-options>
</pre>
</pre>
<blockquote style="background-color: Gold; border: solid thin Goldenrod;">
:<br>option values cannot contain system properties, they cannot be resolved:
: <tt>java.lang.IllegalStateException: WFLYCTL0211: Cannot resolve expression ...</tt><br><br>
</blockquote>


===Log File Path Specification===
===Log File Path Specification===

Revision as of 17:31, 1 November 2016

External

Internal

Overview

GC logging is enabled by default for standalone mode (to verify form which version on). It generates output to $JBOSS_HOME/standalone/log/gc.log.<digit>. The system uses log rotation with the number of log files limited to 5, and the size of each file limited to 3 MB.


Enabling GC Logging in Standalone Mode

TODO.

Enabling GC Logging in Domain Mode

Server Node

The GC logging can be enabled for a specific server node, or generically, across the server group.

To enable GC logging for just one server node, modify the corresponding <jvm> declaration in the host.xml file.

To enable GC logging for an entire server group, edit the <ivm-options> section corresponding to the <jvm> configuration specified for the server group, in domain.xml.

In both cases, add the following JVM options:

<jvm-options>
    <option value="-verbose:gc"/>
    <option value="-Xloggc:${jboss.server.log.dir}/gc.log"/>
    <option value="-XX:+PrintGCDetails"/>
    <option value="-XX:+PrintGCDateStamps"/>
</jvm-options>

option values cannot contain system properties, they cannot be resolved:
java.lang.IllegalStateException: WFLYCTL0211: Cannot resolve expression ...

Log File Path Specification

Host Controller

TODO.