WildFly and Garbage Collection Logging: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 16: | Line 16: | ||
=Enabling GC Logging in Standalone Mode= | |||
=Enabling GC Logging in Domain Mode= | =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, | |||
To enable GC logging for an entire server group, edit the <ivm-options> section corresponding to the [[Domain.xml#.3Cjvm.3E|<jvm>]] configuration specified for the server group, in [[Domain.xml#.3Cjvm.3E|domain.xml]]. | |||
In both cases, add the following JVM options: | |||
<pre> | |||
<jvm-options> | |||
</jvm-options> | |||
</pre> | |||
==Host Controller== | |||
Revision as of 16:54, 1 November 2016
External
- How to enable Garbage Collection (GC) logging in EAP 6 domain mode https://access.redhat.com/solutions/269023
- Preventing GC log file overwrites upon restart in domain mode https://access.redhat.com/solutions/1325293
- How to rotate gc log file configured in domain mode in EAP 6? https://access.redhat.com/solutions/1132613
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
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,
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> </jvm-options>