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.
Distributed and IBM® i - Basic log and trace mode
Distributed and IBM i - HPEL log and trace mode
Log or trace stream | Expected output - traditional log and trace mode | Expected output - HPEL log and trace mode |
---|---|---|
Java trace | SYSPRINT![]() |
|
Java logs (Audit level) | Transformed into write-to-operator (WTO) output to the hard copy logging stream | Same outputs as traditional log and trace mode, plus the following:
|
Java logs (other levels) | SYSOUT or your configured error stream | Same outputs as traditional log and trace mod, plus the following:
|
System.out | SYSPRINT |
|
System.err | SYSOUT |
|
cout (the C or C++ output stream) | SYSPRINT | SYSPRINT |
cerr (the C or C++ error stream) | SYSOUT | SYSOUT |
Native trace | SYSPRINT![]() |
SYSPRINT![]() |
Native Message logs | SYSOUT or your configured error stream | SYSOUT or your configured error stream |
z/OS - Traditional log and trace mode
z/OS - HPEL log and trace mode