Process logs

WebSphere® Application Server processes contain two output streams that are accessible to native code running in the process. These streams are the stdout and stderr streams. Native code, including Java virtual machines (JVM), might write data to these process streams. In addition, JVM provided System.out and System.err streams can be configured to write their data to these streams also.

By default, the stdout and stderr streams are redirected to log files at application server startup, which contain text written to the stdout and stderr streams by native modules (*SRVPGMs, .dlls, .exes, UNIX® libraries, and other modules). By default, these files are stored as profile_root/logs/server_name/native_stderr.log and profile_root/logs/native_stdout.log.

Important: If you turn on the debugging service or verbose Java logging, the size of the native_stderr.log and native_stdout.log files increase in size with each restart of the application server. This situation can cause application server crashes especially on Linux® operating systems where you might have a 2 gigabyte maximum file size. To prevent this problem, consider redirecting the Java exceptions and verbose Java garbage collection to other files.



Related tasks
Diagnosing problems with message logs
Related reference
Process logs settings
Related information
WebSphere Application Server V6: Diagnostic Data
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 8:21:57 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-express-iseries&topic=rtrb_stdlogs
File name: rtrb_stdlogs.html