Hi Tom, Byron, and Sahoo,
I have attempted to consolidate what you have said for the debugging
chapter of the Dev Guide. Here's what I have. Please correct as needed.
*****
To generate class loading messages, use the following asadmin
create-jvm-options command:
asadmin create-jvm-options -verbose\:class
To send the JVM messages to a special JVM log file instead of stdout,
use the following asadmin create-jvm-options commands:
asadmin create-jvm-options -XX\:+LogVMOutput
asadmin create-jvm-options
-XX\:LogFile=${com.sun.aas.instanceRoot}/logs/jvm.log
To send the GlassFish Server messages to the Admin Console instead of
stderr, start the domain in verbose mode as
described in Enabling Verbose Mode.
*****
Rebecca
On 11/30/10 10:38, Tom Mueller wrote:
> Try doing both. With today's 3.1 build, I added:
>
> <jvm-options>-verbose:class</jvm-options>
>
> to the server-config, java-config element of the domain.xml, and then
> ran "asadmin start-domain --verbose" and I see a message printed for
> each class that is loaded.
>
> The JDK verbose messages are printed to stdout, not a logger, so the
> --verbose option on start-domain is needed to see the output. If you
> want the output to go to a log file, you can add the following JVM
> options:
>
> <jvm-options>-XX:+LogVMOutput</jvm-options>
> <jvm-options>-XX:LogFile=${com.sun.aas.instanceRoot}/logs/jvm.log</jvm-options>
>
>
> if you are using the JDK.
>
> Tom
>
> On 11/30/2010 12:21 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?
>>