This section discusses the data that should be collected in the event of an error. You must collect data when any of the following events occurs:
The table below lists the data that needs to be collected for each event.
Table 6-1 Data that needs to be collected for each event
No. | Data | Event | ||
---|---|---|---|---|
Invalid timeout | Abnormal server shutdown | Server process shutdown | ||
1 | Standard output, standard error output | Y | Y | Y |
2 | Error report file | -- | -- | Y |
3 | SDP server definition files | Y | Y | Y |
4 | Adaptor definition files | Y | Y | Y |
5 | Log files | Y | Y | Y |
6 | Trace files | Y#1 | Y | Y |
7 | Adaptor trace information | Y#2 | Y | Y |
8 | Tuple logs | Y#3 | Y | Y |
9 | Thread dump | Y | Y | Y |
10 | OS status | Y | -- | -- |
11 | OS statistics | Y | Y | Y |
12 | Hitachi Web Server error log file#4 | Y | Y | Y |
The table below describes how to collect the data.
Table 6-2 How to collect the data
No. | Data | How to collect |
---|---|---|
1 | Standard output, standard error output | Make a note of (or copy) the messages output to the standard output and standard error output |
2 | Error report file | Copy the files under the following directory: working-directory\ |
3 | SDP server definition files | Copy the files under the following directory: working-directory\conf\ |
4 | Adaptor definition files | Copy the files under the following directory: working-directory\conf\xml\ |
5 | Log files | Copy the files under the following directory: working-directory\logs\ |
6 | Trace files | Copy the files under the following directory: working-directory\trc\ |
7 | Adaptor trace information | Copy the files under the following directory: working-directory\trc\adaptor\ |
8 | Tuple logs | Copy the files under the following directory: working-directory\trc\tuplelog\ |
9 | Thread dump | Collect data by executing the jheapprof command |
10 | OS status | Collect data by executing the netstat command |
11 | OS statistics | Collect performance monitor logs |
12 | Hitachi Web Server error log file | Collect the Hitachi Web Server error log files under the following directory: installation-directory\psb\CC\web\containers\uCSDPAF_Server\logs\ |
The details about how to collect each type of data are described below.
Make a note of (or copy) the messages output to the standard output and standard error output.
Note that all messages related to startup and termination of the SDP server and adaptors are output to the standard output or the standard error output. Some of these messages are also output to log files, but others are not.
An error report file is output in the event of abnormal termination of JavaVM. You can use this file to determine the location and cause of a process shutdown.
The error report file is output directly under the working directory and has the following file name:
hs_err_pidprocess-ID.log
The SDP server definition files include the following files:
Collect these files under the following directory:
working-directory\conf\
If the JavaVM options file for RMI connections is not stored under this directory, also collect that file.
The adaptor definition files include the following files:
Collect these files under the following directory:
working-directory\conf\xml\
The log files include the following:
Collect all the files under the following directory:
working-directory\logs\
For details about the message logs and trace logs, see 6.3.1 Details of log files.
The Hitachi JavaVM log file is the log file to which Hitachi-specific JavaVM logs are output; it is obtained by using extended options added by Hitachi to the standard JavaVM. This file provides more troubleshooting information than the standard JavaVM.
The trace files include various trace files, such as API trace information.
Collect all the files under the following directory:
working-directory\trc\
For details about the API trace information, see 6.3.2 Details of API trace information.
Adaptor trace information is provided as trace files to which the adaptor processing status is output.
Collect the files under the following directory:
working-directory\trc\adaptor\
For details about the adaptor trace information, see 6.3.3 Details of adaptor trace information.
Tuple logs are the log files to which information about the input and output tuples is output.
Collect the files under the following directory:
working-directory\trc\tuplelog\
For details about the tuple logs, see 6.3.4 Details of tuple logs.
A thread dump is a file to which information about the threads running inside Java processes is output.
You use the jheapprof command to collect a thread dump.
For details about how to collect a thread dump and details about the jheapprof command, see 6.3.5 Details of a thread dump.
Collect as the OS status the network information and environment variables. To collect this information, execute the netstat command as follows:
netstat -e > netstat_e.txt |
The OS statistics includes information that enables you to check the status, such as system loading and system performance. You use the OS's performance monitor to collect this information.
While the SDP server is executing, collect at a regular interval the performance monitor logs shown in the table below.
Table 6-3 Performance monitor logs
Object | Instance | Counter |
---|---|---|
Processor | _Total | %Processor Time |
%Privileged Time | ||
%User Time | ||
Memory | -- | Cache Bytes |
Cache Faults/sec | ||
Page Faults/sec | ||
Transition Faults/sec | ||
Transition Faults/sec | ||
Process | _Total | Handle Count |
Page Faults/sec | ||
Private Bytes | ||
Virtual Bytes | ||
Working Set Bytes | ||
java# | %Processor Time | |
%Privileged Time | ||
%User Time | ||
Page Faults/sec | ||
Thread Count | ||
Private Bytes | ||
Virtual Bytes | ||
Working Set Bytes |
We recommend setting 60 seconds as the log collection interval; however, you should determine the appropriate interval on the basis of disk capacity. Setting the collection interval to a large value can reduce the adverse effects of OS statistics collection on performance, but the accuracy of the OS statistics might be compromised.
For details about how to specify the setting, see the OS documentation.
The Hitachi Web Server error log file is used to check and monitor the Web container operating status. Error, warning, and information messages are output to this file.
If you output stream data summary analysis results to a dashboard using the standard adaptors, collect the following log file in the event of a Dashboard Server error (the question mark (?) in the log file name represents a 1- or 2-digit integer):
installation-directory\psb\CC\web\containers\uCSDPAF_Server\logs\user_err?.log