Bill Shannon wrote:
> Kedar!
>
> Kedar JavaNet wrote on 01/03/2011 06:45 PM:
>
>> The other problem (which I am not sure how to address well) is if
>> once you
>> manage to get an invalid JVM option in domain.xml using valid means,
>> your server
>> won't start! So, I guess, I am saying that we should try harder (I
>> tried, way
>> back when, guess it was not enough) not to corrupt domain.xml with
>> invalid JVM
>> options. (I know JVM options are rather unpredictable).
>
> Perhaps we need a "start in safe mode" that causes it to use only
> known good JVM options? Perhaps also ignore user apps and only
> allow the admin console app?
A safe-mode is a great idea... I am not sure that is the right solution
for the problem of creating bogus jvm-options, though.
Maybe we can check that we can start a jvm with the set of jvm options
that would be committed into the domain.xml file...
vbk
>
>