On 29/05/2013 19:49, Brian Burkhalter wrote:
:
Problem is that the String in the NumberFormatException in this case does not
contain the reason, only the offending String. The parseInt() would need to be
changed accordingly to make this intelligible.
I have no strong preference but it does not seem to me that failing to start
the VM is a great plan.
Brian
I think what you have in the webrev is okay because the purpose of this
property is to communicate the value of the AutoBoxCacheMax option. In
other words, this is a special property that only HotSpot should set, it
is not documented/supported and nobody should be setting it on the
command as in the bug report. So if
-XX:AutoBoxCacheMax=<out-of-range-value> is caught and emits a useful
error then I think we are okay.
-Alan.
