Will parsers break if we start logging the GC cause as part of the PrintGC logging?

[Krystal Mok]

Hi Bengt,

Comments inline below:

On Tue, May 8, 2012 at 5:37 AM, Bengt Rutisson <bengt.rutisson at oracle.com>wrote:
>
> Agreed, but I would really like to avoid more VM arguments. If we feel
> uncomfortable with this change I think we should just not do it at this
> point in time.
>
>
Yes, I tend to agree with this approach. And that's why I didn't submit a
patch of PrintGCReason to the upstream. It's not gonna be fun to fix
parsing logic twice in a row.
The change in G1 was okay because there aren't a whole bunch of parsers in
the wild that could parse G1 logs.


> There is a project in planning for a more general logging framework for
> Hotspot. Once that is in place I am sure we will do a major update to the
> GC logging. At that time I guess many parsers will break, so if we feel
> that the proposed change is high risk at the moment I think we should
> postpone it to the major logging overhaul.
>
>
And I've been holding back my new parser work waiting for this...


> I know there has been a JEP written for the new logging framework but that
> JEP is still awaiting publication. Hopefully it will be available soon.
>
> Thanks,
> Bengt
>
>
Thanks,
Kris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/hotspot-gc-use/attachments/20120508/f97bba67/attachment.html