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

Misha Dmitriev misha.dmitriev at oracle.com
Tue May 8 12:56:48 PDT 2012


> Message: 2
> Date: Tue, 08 May 2012 12:42:27 +0200
> From: Bengt Rutisson <bengt.rutisson at oracle.com>
> Subject: Re: Will parsers break if we start logging the GC cause as
> 	part of	the PrintGC logging?
> To: Srinivas Ramakrishna <ysr1729 at gmail.com>
> Cc: "hotspot-gc-use at openjdk.java.net"
> 	<hotspot-gc-use at openjdk.java.net>
> Message-ID: <4FA8F893.604 at oracle.com>
> Content-Type: text/plain; charset="utf-8"
> 
> 
> Thanks for the feedback everyone!
> 
> I think I'll do as Ramki suggested. Add the GC cause to all collectors, 
> but add a switch for users to turn it off. I am not too happy about 
> adding another command line option, but is seems more consistent to do 
> the change for all collectors.

I agree that the "enable by default, and add a flag to disable" is the best choice.

Speaking about HotSpot VM options/flags. I think the biggest problem is not that there are so many flags (I've seen applications with many more), but the fact that the documentation for them is difficult to find, and some flags are always missing from it. If 'java -Xhelp' and 'java -XXhelp' (well, the second option does not even exist) gave me all the available flags for sure, managing them would be much easier.

Misha


More information about the hotspot-gc-use mailing list