4.1 Organization of this chapter
This chapter describes the output destination and the output method of the data used for troubleshooting.
There are the respective default output destinations for the data used for troubleshooting. Additionally, you can separately acquire the data required for troubleshooting, such as the information without using the snapshot log.
The following table describes the organization of this chapter.
Category |
Title |
Reference |
---|---|---|
Explanation |
Types of data used for troubleshooting (When snapshot log is not used) |
|
Application Server log (Systems for executing J2EE applications) |
||
Application Server log (Systems for executing batch applications) |
||
EJB Client Application System Log |
||
Trace based performance analysis |
||
JavaVM thread dump |
||
JavaVM GC Log |
||
Memory Dump |
||
JavaVM log (JavaVM log file) |
||
JavaVM Output Message Logs (Standard Output or Error Report File) |
||
OS Status Information and OS Logs |
||
OS Statistical Information |
||
Application Server definition information |
||
Contents of J2EE server or batch server working directory |
||
Application Server Resource Setting Information |
||
Web Server Logs |
||
JavaVM stack trace information |
||
Event log of the Explicit Memory Management functionality |
||
Information on the execution of the Component Container Administrator setup command (In UNIX) |
For an overview of troubleshooting, how to output the data automatically, setup related to data acquisition and data output, and the output contents of the data, see the following respective chapters:
-
Overview of troubleshooting and how to output the data automatically
-
Setup related to data acquisition and data output
-
Contents output in data