It seems in 3.1, jvm.log is not enabled by default, so if you are
following option #2, then you also need the following setting in domain.xml:
<jvm-options>-XX:LogFile=${com.sun.aas.instanceRoot}/logs/jvm.log</jvm-options>
Sahoo
On Wednesday 01 December 2010 12:17 AM, Sanjeeb Sahoo wrote:
> After setting the appropriate jvm option in domain.xml, you can either
> run:
> 'asadmin start-domain --verbose' in which you shall see the output in
> console
> or
> you can run 'asadmin start-domain' in which case you shall see JVM's
> output in a file called jvm.log or something similar in domain-dir/logs/
>
> Sahoo
> On Tuesday 30 November 2010 11:51 PM, Pete Helgren wrote:
>> I need to get verbose class loading output so that I can diagnose an
>> error. When I add -verbose:class to the jvm options in domain.xml I
>> don't see any changes in the logging. If I start the domain with the
>> --verbose switch I get verbose output but the class loading isn't
>> verbose.
>>
>> Did I miss something?
>>
>