JVM logs(SystemOut and SystemErr logs)
SystemOut and SystemErr logs are created for every WebSphere Application
Server process (application server, cluster member, node agent, and
deployment manager). These logs are known as JVM logs.
Your applications can also write to them by using the print(), println(), and
printStackTrace() methods.
Location:
WAS_install_root/profiles/profile/logs/process
To configure the properties of these logs from the administrative console, select
1.) Troubleshooting → Logs and Trace.
2.) Select the process (application server, cluster member, node agent, and
deployment manager) whose logs you want to configure,
3.) and then click JVM Logs
The SystemOut and SystemErr logs are self-managing. They write to the
specified file until either the maximum file size or a certain time is reached.
When that happens, the current log file is renamed as the current file name
plus the current time stamp. Then a new SystemOut or SystemErr file is
created for further logging. The older log files are called historical log files.
Example– SystemOut.log, the current log file
SystemOut_05.06.07_10.28.48.log, the historical log file
Example that tells us the format of the message that comes in the systemout.log
[7/12/05 14:46:00:264 EDT] 0000001a ApplicationMg A WSVR0221I: Application
started: adminconsole
Each entry can be deciphered as follows:
Time stamp
In the example, the time stamp is [7/12/05 14:46:00:264 EDT].
The time stamp is formatted using the locale of the process where it is
formatted. It includes a fully qualified date (for example MM/DD/YY), 24-hour
time with millisecond precision, and a time zone.
Thread ID
In the example, the thread ID is 0000001a.
The thread ID is an eight-character hexadecimal value that is generated from
the hash code of the thread that issued the message.
Short name
In the example, the short name is ApplicationMg.
The short name is the abbreviated name of the component that issued the
message. This name is typically the class name of a WebSphere Application
Server component and would be some other identifier for applications.
Event type
In the example, the event type is A.
The event type is a one character field that indicates the type of the message.
The possible values are:
– F - fatal message
– E - error message
– W - warning message
– A - audit message
– I - informational message
– C - configuration message
– D - detail message
– O - message that was written directly to System.out by an application or
internal components
– R - message that was written directly to System.err by the user application
or internal components
– Z - a placeholder to indicate that the type was not recognized
_ Message Identifier
In the example, the message identifier is WSVR0221I.
The message identifier is a string that is nine characters in length and is in the
form CCCC1234X. The first four characters (CCCC) indicate the WebSphere
Application Server component that issued the message. The next four
characters (1234) indicate the specific message that the component is
issuing. The last character (X) indicates the severity of the message. Its value
is either I (informational), W (warning), or E (error).
