View the JVM log files to determine problems within application environments.
The JVM logs contain print data written by applications. The application can write this data directly in the form of System.out.print(), System.err.print(), or other method calls. The application can also write data indirectly by calling a JVM function, such as an Exception.printStackTrace(). In addition, the System.out JVM log contains system messages written by the WebSphere Application Server.
If you allow the application server to
format the application data, it is printed in the normal z/OS trace format.
If you do not allow the application server to format the application data,
the raw text is printed, which is much harder to analyze.
You can format application data to look like WebSphere
Application Server system messages by using the Installed Application Output
field of the JVM Logs properties
panel, or as plain text with no additional formatting. WebSphere Application
Server system messages are always formatted. Depending on how the JVM log
is configured, formatted messages can be written to the JVM logs in either
basic or advanced format.
Message events displayed in basic format use the following format. The notation <name> indicates mandatory fields that will always appear in the basic format message. The notation [name] indicates optional or conditional fields that will be included if they can be determined.
<timestamp><threadId><shortName><eventType>[className][methodName]<message>
Message events displayed in advanced format use the following format. The notation <name> is used to indicate mandatory fields that will always appear in the advanced format for message entries. The notation [name] is used to indicate optional or conditional fields that will be included if they can be determined.
<timestamp><threadId><eventType><UOW><source=longName>[className] [methodName]<Organization><Product><Component> [thread=threadName]<message>
1| 2005/03/02 17:31:17.641 01 t=8FB718 c=UNK key=S2 (13007002) 2| ThreadId: 0000004e 3| FunctionName: com.ibm.ws.sm.workspace.impl.WorkSpaceManagerImpl 4| SourceId: com.ibm.ws.sm.workspace.impl.WorkSpaceManagerImpl 5| Category: AUDIT 6| ExtendedMessage: BBOO0222I: WKSP0023I: Workspace configuration consistency check is disabled.
Line number | Component | Description |
---|---|---|
1 | 2005/03/02 17:31:17.641 01 | Date / timestamp / 2-digit record version number |
1 | t=8FB718 | MVS TCB (thread) Address |
1 | c=UNK | Request correlation information |
1 | key=S2 | State/Key (S=Supervisor,P=Problem) |
1 | (13007002) | Trace Point Identifier |
2 | ThreadId: 0000004e | Thread Identifier (TID) |
3 | FunctionName: com.ibm.ws.sm.workspace.impl.WorkSpaceManagerImpl | Function name |
4 | SourceId: com.ibm.ws.sm.workspace.impl.WorkSpaceManagerImpl | Source Identifier |
5 | Category: AUDIT | Category |
6, 7 | ExtendedMessage: ... | Log message |