[jboss-jira] [JBoss JIRA] (WFCORE-3996) GC logging is not working on Java 9

[James Perkins (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619091#comment-13619091 ] 

James Perkins commented on WFCORE-3996:
---------------------------------------

For completeness too so we know our other options here's the help output ({{java -Xlog:help}}).
{code}
-Xlog Usage: -Xlog[:[what][:[output][:[decorators][:output-options]]]]
     where 'what' is a combination of tags and levels of the form tag1[+tag2...][*][=level][,...]
     Unless wildcard (*) is specified, only log messages tagged with exactly the tags specified will be matched.

Available log levels:
 off, trace, debug, info, warning, error

Available log decorators: 
 time (t), utctime (utc), uptime (u), timemillis (tm), uptimemillis (um), timenanos (tn), uptimenanos (un), hostname (hn), pid (p), tid (ti), level (l), tags (tg)
 Decorators can also be specified as 'none' for no decoration.

Available log tags:
 add, age, alloc, aot, annotation, arguments, attach, barrier, biasedlocking, blocks, bot, breakpoint, cds, census, class, classhisto, cleanup, codecache, compaction, compilation, constraints, constantpool, container, coops, cpu, cset, data, datacreation, defaultmethods, dump, ergo, exceptions, exit, fingerprint, freelist, gc, handshake, hashtables, heap, humongous, ihop, iklass, init, inlining, interpreter, itables, jit, jni, jvmti, liveness, load, loader, logging, mark, marking, membername, memops, methodcomparator, metadata, metaspace, mmu, module, monitorinflation, monitormismatch, nmethod, normalize, objecttagging, obsolete, oopmap, os, pagesize, patch, path, perf, phases, plab, promotion, preorder, protectiondomain, ref, redefine, refine, region, remset, purge, resolve, safepoint, scavenge, scrub, smr, stacktrace, stackwalk, start, startuptime, state, stats, stringdedup, stringtable, stackmap, subclass, survivor, sweep, table, task, thread, tlab, time, timer, update, unload, unshareable, verification, verify, vmoperation, vmthread, vtables, workgang
 Specifying 'all' instead of a tag combination matches all tag combinations.

Described tag combinations:
 logging: Logging for the log framework itself

Available log outputs:
 stdout, stderr, file=<filename>
 Specifying %p and/or %t in the filename will expand to the JVM's PID and startup timestamp, respectively.

Some examples:
 -Xlog
     Log all messages using 'info' level to stdout with 'uptime', 'levels' and 'tags' decorations.
     (Equivalent to -Xlog:all=info:stdout:uptime,levels,tags).

 -Xlog:gc
     Log messages tagged with 'gc' tag using 'info' level to stdout, with default decorations.

 -Xlog:gc,safepoint
     Log messages tagged either with 'gc' or 'safepoint' tags, both using 'info' level, to stdout, with default decorations.
     (Messages tagged with both 'gc' and 'safepoint' will not be logged.)

 -Xlog:gc+ref=debug
     Log messages tagged with both 'gc' and 'ref' tags, using 'debug' level, to stdout, with default decorations.
     (Messages tagged only with one of the two tags will not be logged.)

 -Xlog:gc=debug:file=gc.txt:none
     Log messages tagged with 'gc' tag using 'debug' level to file 'gc.txt' with no decorations.

 -Xlog:gc=trace:file=gctrace.txt:uptimemillis,pids:filecount=5,filesize=1m
     Log messages tagged with 'gc' tag using 'trace' level to a rotating fileset of 5 files of size 1MB,
     using the base name 'gctrace.txt', with 'uptimemillis' and 'pid' decorations.

 -Xlog:gc::uptime,tid
     Log messages tagged with 'gc' tag using 'info' level to output 'stdout', using 'uptime' and 'tid' decorations.

 -Xlog:gc*=info,safepoint*=off
     Log messages tagged with at least 'gc' using 'info' level, but turn off logging of messages tagged with 'safepoint'.
     (Messages tagged with both 'gc' and 'safepoint' will not be logged.)

 -Xlog:disable -Xlog:safepoint=trace:safepointtrace.txt
     Turn off all logging, including warnings and errors,
     and then enable messages tagged with 'safepoint' using 'trace' level to file 'safepointtrace.txt'.
{code}

> GC logging is not working on Java 9
> -----------------------------------
>
>                 Key: WFCORE-3996
>                 URL: https://issues.jboss.org/browse/WFCORE-3996
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Scripts
>            Reporter: Rostislav Svoboda
>            Assignee: Radovan Stancel
>            Priority: Blocker
>              Labels: Java11, blocker-WF14
>
> GC logging is not working on Java 9. This is related to the fact G1 GC is default and there are changes in configuration option.
> {code}
> GC_LOG="true" ./standalone.sh
> {code}
> Java 8:
> {code}
> JAVA_OPTS:  -server -verbose:gc -Xloggc:"/Users/rsvoboda/TESTING/7.2.0.CD12.CR1/jboss-eap-7.2/standalone/log/gc.log"
>  -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5
>  -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -Xms1303m -Xmx1303m -XX:MetaspaceSize=96M 
>  -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> {code}
> Java 9:
> {code}
> JAVA_OPTS:  -server -Xms1303m -Xmx1303m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m
>  -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> {code}



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)