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.
>
>
>
>
> --
>
> [Message sent by forum member 'najmi']
>
> View Post: http://forums.java.net/node/874299
>
>