Feedback requested: HotSpot GC logging improvements

[Chi Ho Kwok]

Talking about a new log format... Is it possible to send the log events to
the java.util.logging system too so we can do the whole redirection, write
to file or integration in log4j via adapters ourselves, if we choose to?
Just dump the string message in a LogRecord and put all parameters into
setParameters(), so you can access either the string / formatted message or
get a machine readable version by calling getParameters(). Parameters are
arrays like ["GCNew", time spent, prev usage, current usage, etc], where the
first field defines the type, and the other parameters' interpretation
depend on the type.

Okay, with this, you can't just add a some command line flags to reconfigure
GC logging, but this makes integrating GC related things in apps much
easier, you can write a { if concurrent collector failed - send the admin an
email that the app stopped for $x seconds, please fix } script in a minute;
or if { gc overhead > 10% then maybe you should increase the heap size }
trigger. No more writing scripts that parse the output of the gc log to
check for weird things. No more parsing at all.


Chi Ho Kwok

On Fri, May 7, 2010 at 7:05 AM, Rainer Jung <rainer.jung at kippdata.de> wrote:

> On 07.05.2010 00:00, Peter B. Kessler wrote:
> > +1 on including the command line arguments (or maybe the settings those
> provoke inside the VM) in the log file.  For settings that change over time,
> e.g., because of ergonomics, it would be good to have a way to see those,
> too.  Maybe "a new log file format" allows that to happen.
>
> +1
> _______________________________________________
> hotspot-gc-use mailing list
> hotspot-gc-use at openjdk.java.net
> http://mail.openjdk.java.net/mailman/listinfo/hotspot-gc-use
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/hotspot-gc-use/attachments/20100507/08fc5ff5/attachment.html