Enable verbosegc for the following
versions of WebSphere Application Server:
Note: While verbose garbage collection logging has
negligible impact on the performance of your system, analysis of the
collected verbosegc data can lead to improved performance.
Enabling 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.
- 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. |
|
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.
- Click Save. The parameters will take affect at the next
Deployment Manager restart.
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 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.
|
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.
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.
|
Enabling verbosegc on releases of Version 5.1 and 5.0
- In the Administrative Client, expand Servers and then click on
Application Servers.
- Click on the server that is encountering the "OutOfMemory" condition.
- Under the Additional Properties section, click Process
Definition.
- Under the Additional Properties section, click Java Virtual
Machine.
- Select the check box Verbose garbage collection.
- Click Apply.
- At the top of the Administrative Client, click Save to save the
changes to your configuration.
- Stop and start the Application Server.
- 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
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.
|
Enabling verbosegc on releases of Version 5.1 and 5.0 Deployment
Manager
- Open the Administrative Console.
- Expand System Administration.
- Click Deployment Manager.
- Click Process Definitions under Additional Properties.
- 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
Deployment Manager restart.
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 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. Please ensure there is adequate file system
space when enabling this option.
|
Enabling verbosegc on releases of Version 5.1 and 5.0 Node
Agent
- Open the Administrative Console.
- Expand System Administration.
- Click Node Agents.
- Click on the Node Agent.
- Click Process Definitions under Additional Properties.
- 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.
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 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. Please ensure there is adequate file system
space when enabling this option.
|
Enabling verbosegc on releases of Version 4.0 Advanced Edition
- In the Administrative Client, select the Application Server and go to
the JVM Settings tab.
- Click Advanced JVM Settings.
- Select the check box Enable garbage collection verbose mode.
- Click OK.
- Click Apply.
- Stop and restart the Application Server.
- The verbose garbage collection output will be placed in the
stderr file for the Application Server.
Note:
- For an HP-UX system, add the following parameter to the
command line arguments field located on the Advanced JVM
Settings panel:
-Xverbosegc:file=<name> |
Where <name> is a valid fully qualified filename.
|
Enabling verbosegc on releases of Version 4.0 Advanced Single Server
Edition
- Edit the server-cfg.xml file found in the directory,
install_root/config.
- Search on command and find, commandLineArgument="".
- In the empty quotes, add -verbosegc so that it looks like the
following:
commandLineArgument="-verbosegc" |
|
- Stop and restart the application server.
Note:
- For an HP-UX system, also add to the following parameter
to the commandLineArgument:
-Xverbosegc:file=<name> |
Where <name> is a valid fully qualified filename.
|
Enabling verbosegc on releases of Version
3.5
- In the Administrative Client, select the Application Server and go to
the General tab.
- Add the following line to the Command line arguments
field:
- Click Apply.
- Stop and restart the Application Server.
- The verbose garbage collection output will be placed in the
stderr file for the Application Server.
Note:
- If using Solaris, enter the argument twice as follows:
|