From: Tom Mueller <tom.mueller_at_oracle.com>
Date: Thu, 15 Dec 2011 09:06:23 -0600

One possible reason for not getting a jvm.log file is that the default
JVM option that causes this to be created was removed in 3.1 because it
is incompatible with other JVMs. In GF 3.0, this option is as follows:

-XX:LogFile=${com.sun.aas.instanceRoot}/logs/jvm.log

To add it into a 3.1 install, run:

asadmin create-jvm-options
'-XX\:LogFile=${com.sun.aas.instanceRoot}/logs/jvm.log'

(note: the : has to be escaped with \)

Tom