Open stubarlow opened 5 years ago
Hi Stubarlow,
It looks like the parser was confused by some part of the log output in your log file. Could you please attach a sample log file to this issue containing the offending line(s)?
Best regards, Jörg
Hi Jörg. There were 7 occurrences of the offending event over a 3 day period. Each occurrence results in 4 separate log entries. There's one example in that sample I attached. Let me know if you need more data. Thanks!
Hi. I found a number of WARNING messages after parsing my gc log. Version 1.36-SNAPSHOT jdk1.8.0_144
parser output
gc log entry
2019-03-18T12:19:49.065+0100: 502562.066: [Preclean SoftReferences, 0.0001084 secs]2019-03-18T12:19:49.065+0100: 502562.066: [Preclean WeakReferences, 0.0000868 secs]2019-03-18T12:19:49.066+0100: 502562.066: [Preclean FinalReferences, 0.0000938 secs]2019-03-18T12:19:49.066+0100: 502562.066: [Preclean PhantomReferences, 0.0000054 secs]2019-03-18T12:19:49.073+0100: 502562.073: [CMS-concurrent-preclean: 0.008/0.008 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
Great tool by the way. I've just started using it. Apologies if I inadvertently created this problem myself by setting incorrect JVM parameters.
JVM Parameters
-XX:+PrintGCDetails -XX:+PrintReferenceGC -XX:+PrintGCApplicationStoppedTime -XX:+PrintTenuringDistribution -Xloggc:/path/to/log/gc.log -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=2 -XX:GCLogFileSize=10m