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.
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 |