interesting log entries
ysr1729 at gmail.com
Fri Aug 1 17:03:09 UTC 2014
Use the "jvm age" timestamp. That seems to be monotonically increasing, and
doesn't present the issues with the date-stamp on account of NTP etc.
On Fri, Aug 1, 2014 at 4:32 AM, Kirk Pepperdine <kirk at kodewerk.com> wrote:
> I’ve run into this in a 1.7.0_40 with G1GC, with -XX:+PrintGCDetails,
> -XX:+PrintApplicationStoppedTime -XX:+PrintTenuringDistribution and it’s
> using the rolling logs feature.
> The log is riddled with all kinds of different variants of date going
> backwards and time stamp going forward for backwards. My guess is NTP is
> involved here but there must also be some bug in the logging to allow
> things to travel in different directions and/or at different rates.
> 2014-06-16T01:41:02.478+0200: 7324.015: Total time for which application
> threads were stopped: 0.0009980 seconds
> 2014-06-16T01:41:02.479+0200: 7324.016: Application time: 0.0008090 seconds
> 2014-06-16T01:41:02.479+0200: 7324.016: Total time for which
> a1:40:22.957+0200: 7407.019: Application time: 0.0001020 seconds
> 2014-06-16T01:40:22.958+0200: 7407.020: Total time for which application
> threads were stopped: 0.0012800 seconds
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the hotspot-gc-dev