Because these options cause the server to not be runnable with other
JVMs, specifically JRockit.
The following RFE was created to support JVM-specific options:
http://java.net/jira/browse/GLASSFISH-16247
A release for this hasn't been determined, but a vote for the RFE
couldn't hurt.
Tom
On 3/21/2012 2:29 PM, Farrukh Najmi wrote:
>
> Thank you Sahoo! You are a life saver! That was it. I now have a
> jvm.log file.
>
> May I ask why these two options are not in the default domain.xml
> generated during GF install?
>
> <jvm-options>-XX:LogFile=${com.sun.aas.instanceRoot}/logs/jvm.log</jvm-options>
>
> <jvm-options>-XX:+LogVMOutput</jvm-options>
>
> Seems to me that would be the right thing to do.
>
> On 03/21/2012 03:06 PM, Sahoo wrote:
>> AFAIK, you also need
>>
>> <jvm-options>-XX:+LogVMOutput</jvm-options>
>>
>> as I wrote once here [1].
>>
>> Sahoo
>>
>> [1]
>> http://weblogs.java.net/blog/ss141213/archive/2012/02/23/getting-verbose-class-loading-output-glassfish?force=398
>>
>> On Wednesday 21 March 2012 11:49 PM, forums_at_java.net wrote:
>>> After several months I am again seeing Glassfish 3.1.2 exit during
>>> heavy
>>> transaction load leaving no jvm.log file anywhere that I can find.
>>>
>>> In my domain.xml file I have the following:
>>>
>>> <jvm-options>-XX:LogFile=${com.sun.aas.instanceRoot}/logs/jvm.log</jvm-options>
>>>
>>>
>>> This is a serious reliability issue and I would be very grateful if
>>> someone
>>> from the GF team could help. The scneario is reproducable on demand at
>>> present and I would be glad to work with someone from teh GF dev
>>> team to
>>> narrow this down. Thanks for your help.
>