Process logs for native code
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.
(Dist) 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 (.dlls, .exes, UNIX libraries, and other modules). By default, these files are stored as...
- profile_root/logs/server/native_stderr.log
- profile_root/logs/native_stdout.log
(iSeries) 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/native_stderr.log
- profile_root/logs/native_stdout.log
If we 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 we 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.
(Linux) We can increase the maximum file size beyond the 2 gigabyte file size limit if we enable Large File Support (LFS). See the operating system documentation.