JEP 245: Validate JVM Command-Line Flag Arguments (original) (raw)

kedar mhaswade kedar.mhaswade at gmail.com
Fri Apr 17 12:24:03 UTC 2015

+1. Will this also make the 'java command line' a public interface of the Java platform?

Martijn -- in your case, would the ​examination of the output of the ​ flag -XX:+PrintFlagsFinal have helped? But then that flag makes the JVM startup print values of the JVM options as represented by the internals, not how one specified on the command line. (e.g. uintx GCTimeLimit = 98 {product} ).

On Fri, Apr 17, 2015 at 3:19 AM, Martijn Verburg <martijnverburg at gmail.com> wrote:

Hi all,

This would be of great benefit to the tools space, we just spent the last couple of days digging into GC flag (invalid) values causing 'interesting' things to happen. Having info messages instead of a JVM crash will also reduce the number of JVM crashes we see out there. WRT to performance tuning this will allow people to rapidly change settings in test with more confidence. Anyhow, thanks for proposing this JEP!

Cheers, Martijn On 17 April 2015 at 00:54, <mark.reinhold at oracle.com> wrote: > New JEP Candidate: http://openjdk.java.net/jeps/245 > > - Mark >

More information about the hotspot-dev mailing list