Date Created: Tue 12-Feb-2008

Related Document Categories:

Get my WebSphere Application Server course here >> http://www.themiddlewareshop.com/products/


Enabling Verbose Garbage Collection verbosegc on releases of Version 6.0 and 6.1

In the Administrative Console, expand Servers and then click on Application Servers.

Click on the server that is encountering the "OutOfMemory" condition.

On the Configuration tab, under Server Infrastructure, expand Java and Process Management, and click Process Definition.



Under the Additional Properties section, click Java Virtual Machine.



Select the Verbose garbage collection check box.



Click Apply.

At the top of the Administrative Client, click Save to apply changes to the master configuration.

Stop and restart the Application Server.

If you wish to add extra JVM parameters read below:

The verbose garbage collection output is written to either native_stderr.log or native_stdout.log for the Application Server, depending on the SDK operating system as follows:

For AIX®, Microsoft® Windows®, or Linux®:
native_stderr.log


For Solaris™ or HP-UX:
native_stdout.log

Notes:
For an HP-UX system, add the following parameter to the Generic JVM arguments on the Java Virtual Machine Settings page:

-Xverbosegc:file=<name>

Where <name> is a valid fully qualified filename.

For a Solaris system, add the following parameters to the Generic JVM arguments on the Java Virtual Machine Settings page:

-XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC

The -XX:+PrintHeapAtGC parameter will generate a large amount of logging to the native_stdout.log file. Ensure there is adequate file system space when enabling this option.

If you make changes to the JVM parameters you must restart the Application Server.
------------------------------------------------------------------


Enabling verbosegc on Version 6.0 Deployment Manager
Open the Administrative Console.




Expand System Administration.

Click Deployment Manager.

Expand Java and Process Management.

Click Process Definition.


Click Java Virtual Machine






Select the Verbose Garbage Collection check box.



Click OK.

Click Save. The parameters will take affect at the next Deployment Manager restart.

If you wish to add extra JVM parameters read below:

For an HP-UX system, add the following parameter to the Generic JVM arguments on the Java Virtual Machine Configuration page:

-Xverbosegc:file=<name>

Where <name> is a valid fully qualified filename.

For a Solaris 1.4 JVM system, add the following parameters to the Generic JVM arguments on the Java Virtual Machine Configuration page. This applies to releases of WebSphere Application Server V5.1 and higher:

-XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC

The -XX:+PrintHeapAtGC parameter will generate a large amount of logging to the native_stdout.log file. Ensure there is adequate file system space when enabling this option.

If you make changes to the JVM parameters you must restart the Deployment Manager.
---------------------------------------------------------------

Enabling verbosegc on Version 6.0 Node Agent
Open the Administrative Console.


Expand System Administration.


Click Node Agents.



Click on the Node Agent.



Expand Java and Process Management.




Click Process Definition.



Click Java Virtual Machine.


Select the Verbose Garbage Collection check box.



Click OK.


Click Save.


Click Save. The parameters will take affect at the next Node Agent restart.

If you wish to add extra JVM parameters read below:

Notes:
For an HP-UX system, add the following parameter to the Generic JVM arguments on the Java Virtual Machine Configuration page:

-Xverbosegc:file=<name>

Where <name> is a valid fully qualified filename.



For a Solaris 1.4.X JVM system, add the following parameters to the Generic JVM arguments on the Java Virtual Machine Configuration page. This applies to releases of WebSphere Application Server V5.1 and higher:

-XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC

The -XX:+PrintHeapAtGC parameter will generate a large amount of logging to the native_stdout.log file. Ensure there is adequate file system space when enabling this option.

If you make changes to the JVM parameters you must restart the Nodeagent.

References:
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21114927

Get my WebSphere Application Server course here >> http://www.themiddlewareshop.com/products/

Steve Robinson - IBM Champion 2013

About Me

Steve Robinson has been working in IT for over 20 years and has provided solutions for many large-enterprise corporate companies across the world. Steve specialises in Java and Middleware.

In January 2013, I was awarded the prestigous 'IBM Champion' accolade.


  • Linked In
  • Twitter
  • About Me
  • My Blog
  • Contact Me

Read my books?

IBM WebSphere Application Server 8.0 Administration Guide

IBM WebSphere Application Server 8.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide

WebSphere Categories

Other Categories