3.2 Overview of data acquisition settings
For certain materials required for troubleshooting, you need to specify collection of the material before starting the operations. For example, if you do not make settings in advance for collecting material, you cannot acquire the statistical information of the OS, user dumps (in Windows) or core dumps (in UNIX), or GC log of JavaVM. Hitachi recommends that you obtain this data because it is required for troubleshooting.
If the material can be collected with default settings, specific settings are not required, however, if you want to change the log output destination and size, edit the Easy Setup definition file and user definition file to change the settings.
The following table describes handling of the data required for troubleshooting, data that require in advance settings, and the data for which you must change the settings.
|
Data necessary for troubleshooting |
Data that require in advance settings or data for which the settings must be changed |
|
|---|---|---|
|
Log of Application Server |
Message log |
|
|
User log |
||
|
Exception log |
||
|
Maintenance log |
||
|
EJB client application system log |
Message log |
|
|
User log |
||
|
Exception log |
||
|
Maintenance log |
||
|
Trace based performance analysis |
Trace based performance analysis file |
|
|
Thread dumps of JavaVM |
JavaVM material |
|
|
GC logs of JavaVM |
JavaVM material |
|
|
Memory dump |
|
|
|
Hitachi JavaVM log file |
JavaVM material |
|
|
Error report files |
-- |
|
|
Compilation replay file |
-- |
|
|
OS state or log |
-- |
|
|
Statistical information of OS |
Statistical information of OS |
|
|
Definition information |
-- |
|
|
Operation directory |
-- |
|
|
Resource setting |
-- |
|
|
Web server log |
-- |
|
|
JavaVM stack trace |
-- |
|
|
Event log of Explicit Memory Management functionality |
JavaVM material |
|
- Legend:
-
--: No data for in advance settings and no data to change the settings
- Note:
-
Besides this table, there is an operation information file for the data that requires in advance settings and the data requires changes in settings. An operation information file is a file used for acquiring the operation information, such as server performance for each functionality and the resource information. You can use this file for operation monitoring of systems. You can acquire the operation information file by default.
- #
-
For details about the system logs of EJB client applications, see 3.8 System log output for EJB client application in the uCosminexus Application Server EJB Container Functionality Guide.
This section gives an overview on the types and settings of the data that require in advance settings and the data that requires changes in the settings, for each system executed that executes an application.