Log streams and expected output
Investigating the logging and tracing output for the application server is an excellent way to observe performance, diagnose problems, and gain a general understanding of how the application server is working within your environment. The expected output locations for logging and trace information can be different depending on the operating system on which the application server is running.
Note: This topic references one or more of the application server log files. As a
recommended alternative, you can configure the server to use the High Performance Extensible Logging
(HPEL) log and trace infrastructure instead of using SystemOut.log ,
SystemErr.log, trace.log, and
activity.log files on distributed and IBM®
i systems. You can also use HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access all of your log and trace
information using the LogViewer command-line tool from your server profile bin directory. See the
information about using HPEL to troubleshoot applications for more
information on using HPEL.
Log or trace stream | Expected output - basic log and trace mode | Expected output - HPEL log and trace mode |
---|---|---|
Java™ trace | Trace.log. You must have tracing enabled. |
|
Java logs |
|
|
System.out stream |
|
|
System.err stream | SystemErr.log |
|
cout (the C or C++ output stream) | Native stdout | Native stdout |
cerr (the C or C++ error stream) | Native stderr | Native stderr |