what errors will come in native_stdout.log? what about native_stderr.log

 

native_stdout.log and native_stderr.log: are usually blank. Their function is unknown at this time. Enabling verbose garbage collection logging is often required when tuning and debugging many issues. The verbose garbage collection output is written to either native_stderr.log or native_stdout.log or the Application Server depending on the SDK operating system as follows:

native_stderr.log --- AIX, MS Windows, Linux
native_stdout.log --- Solaris, HP-UX

 

Enabling Verbose Garbage Collection verbose GC 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.

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