In standalone mode, you can turn on GC logging relatively easily by adding the set of options to standalone.conf or uncommenting the section in standalone.sh/bat.

Turning it on for managed servers in domain mode is much more complex. The main options to control GC logging can be added to the <jvm-options> in <jvm>s, but the log location in "-Xloggc:" is server specific so they do not overwrite each other. As noted on https://developer.jboss.org/thread/237355 you cannot use a substitution like "${jboss.server.log.dir}" since they are done by the host controller once and not per-server, and that is not set at resolution time. This means that every individual server in host.xml needs a <jvm><jvm-options> configuration to set that, which is tedious and error prone.

It would be good to provide a way of configuring GC logging for managed servers in domain mode which is simpler and less likely to cause mistakes. Two mechanisms that may be options would be the following, but there may be others:

• Supporting per-server substitutions in domain.xml <jvm> definitions, so ${jboss.server.log.dir} could be used
• a <gc-logging> option similar to <heap>, with a few options and WF knows how to add the correction options. This may require that WF knows more about which java implementation is being used