Log and trace settings


 

+

Search Tips   |   Advanced Search

 

To set logging and trace settings for the server.

To view this admin console page, click:

Diagnostic Trace

Initial trace state for a server process. Settings are read at server startup. We can also change many of the trace service properties or settings while the server process is running.

JVM Logs

The JVM logs are created by redirecting the System.out and System.err streams of the JVM to independent log files. WAS writes formatted messages to the System.out stream. In addition, apps and other code can write to these streams using the print() and println() methods defined by the streams.

Process Logs

WAS 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 JVMs, 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.

IBM Service Logs

The service log contains both the WAS messages that are written to the System.out stream and some special messages that contain extended service information that is normally not of interest, but can be important when analyzing problems. There is one service log for all WAS JVMs on a node, including all appservers. The IBM Service log is maintained in a binary format and requires a special tool to view. This viewer, the Log and Trace Analyzer, provides additional diagnostic capabilities. In addition, the binary format provides capabilities that are utilized by IBM support organizations.

Change Log Level Details

Enter a log detail level that specifies the components, packages, or groups to trace. The log detail level string must conform to the specific grammar described in this topic. We can enter the log detail level string directly, or generate it using the graphical trace interface.




 

Related tasks

Diagnose problems with message logs