7.2.1 Information required for investigating errors
- Organization of this subsection
(1) Checking the phenomenon
In case of failure, check and consolidate the status as to in which environment what phenomenon occurred. The following table describes the items to be checked in case of failure:
|
No. |
Item to be checked |
Machine on which error is detected |
|||||
|---|---|---|---|---|---|---|---|
|
Machine on which HCSC server is running |
Machine on which operating environment is running |
Machine on which service requester is running |
Machine on which service component is running |
Machine on which database is running |
|||
|
1 |
Basic points |
Time when failure occurred |
Confirm as to when (from when) the error occurred. |
||||
|
2 |
Operation executed just before failure occurrence |
Confirm as to which operations were performed when the error occurred. For details about the troubleshooting for a failure that occurred during setup or unsetup of the system, see 7.5 Troubleshooting During System Setup and Unsetup. |
|||||
|
3 |
Machine on which error was detected |
Confirm as to on which machine the error was detected.
|
|||||
|
4 |
Error contents |
Specifically mention the type of phenomenon that occurred. For the procedure for recovery from an HCSC server failure, see 7.9 Restoration methods when HCSC server error occurred. |
|||||
|
5 |
Operating environment |
Version of Service Platform |
Y |
-- |
-- |
-- |
-- |
|
6 |
J2EE server product name and version |
-- |
-- |
Y |
Y |
-- |
|
|
7 |
Database product name and version |
-- |
-- |
-- |
-- |
Y |
|
|
8 |
OS type and version |
Y |
Y |
Y |
Y |
Y |
|
|
9 |
Number of processors |
Y |
Y |
Y |
Y |
Y |
|
|
10 |
Memory |
Y |
Y |
Y |
Y |
Y |
|
|
11 |
Virtual memory |
Y |
Y |
Y |
Y |
Y |
|
|
12 |
Java version |
Y |
Y |
Y |
Y |
Y |
|
|
13 |
Patch applicable status |
Y |
Y |
Y |
Y |
Y |
|
|
14 |
Reproducibility |
Reproducibility |
Confirm whether it can be reproduced. |
||||
|
15 |
Occurrence frequency |
In the case of reproducibility, confirm the frequency of error occurrence. |
|||||
|
16 |
Configuration changes |
Whether changed when occurred |
Confirm whether the coding or environment was changed before occurrence of corresponding error. |
||||
|
17 |
Contents of changed places |
If there are any changes, then specifically mention the changed contents. |
|||||
- Legend:
-
Y: Must be confirmed.
--: Confirmation not required.
(2) Failure information that must be acquired
Before you can investigate a failure that occurred on a service platform, you must acquire necessary information according to the type of failure as shown in the following table.
- Important note
-
Note that there are items that require settings for acquiring error information. For details about error information acquisition, see 7.3 Acquiring failure information. For details about the place where acquired error information is output, see 7.3 Acquiring failure information and 7.4 Viewing the failure information that has been output.
Note that, for the items for which acquisition of failure information is not set, you might need to acquire failure information if investigation requires it, although you usually do not need to perform investigation or inquiry about the failure.
|
No. |
Information that can be acquired |
Error type |
||||
|---|---|---|---|---|---|---|
|
When error message or exception is output by user program |
When error occurs in service component invoking request (7.7) |
When error occurs in operations (command operations or operations from screens of operating environment) (7.6) |
||||
|
1 |
Material for the Service Platform |
P |
P |
P |
||
|
2 |
P |
P |
-- |
|||
|
3 |
-- |
S |
-- |
|||
|
4 |
S |
S |
-- |
|||
|
5 |
HCSC server configuration definition file |
-- |
P |
P |
||
|
6 |
HCSC server setup definition file |
-- |
P |
P |
||
|
7 |
HCSC server runtime definition file: |
-- |
P |
P |
||
|
8 |
HCSC-Manager definition file |
-- |
P |
P |
||
|
9 |
The HCSC-Manager command definition file |
-- |
P |
P |
||
|
10 |
HCSC-Messaging command definition file |
-- |
P |
P |
||
|
11 |
Service-information change definition file |
-- |
S |
S |
||
|
12 |
User-defined reception runtime definition file |
-- |
S |
S |
||
|
13 |
SOAP fault operation definition file |
-- |
S |
S |
||
|
14 |
Client definition file |
-- |
S |
S |
||
|
15 |
Logs of J2EE server#, redirector, and server management commands |
P |
P |
S |
||
|
16 |
Logs of Administration Agent, Management Agent, and Management Server (Integrated log) |
P |
S |
P |
||
|
17 |
DB Connector (Activity log of resource adapter) |
P |
P |
P |
||
|
18 |
EJB client application log |
P |
P |
-- |
||
|
19 |
User log |
P |
S |
-- |
||
|
20 |
Definition information |
Setup file of Component Container |
S |
P |
P |
|
|
21 |
Setup file of Manager |
S |
P |
P |
||
|
22 |
DB Connector property information setup in dbcon-xadisplayname |
S |
P |
S |
||
|
23 |
DB Connector property information setup in dbcon-nodisplayname |
S |
S |
P |
||
|
24 |
Start stop message log |
-- |
S |
P |
||
|
25 |
Message log for J2EE server# |
S |
P |
P |
||
|
26 |
Method trace |
S |
P |
P |
||
|
27 |
Line trace |
S |
P |
P |
||
|
28 |
Definition information |
Setup information of Reliable Messaging configuration property |
S |
P |
P |
|
|
29 |
Trace |
S |
P |
-- |
||
|
30 |
Application log |
S |
P |
-- |
||
|
31 |
Definition information |
Definition file (SOAP Communication Infrastructure) |
S |
P |
-- |
|
|
32 |
Server definition files (SOAP Communication Infrastructure) |
S |
P |
-- |
||
|
33 |
Trace |
S |
P |
-- |
||
|
34 |
Application log |
S |
P |
-- |
||
|
35 |
Definition information |
Common definition file (JAX-WS engine) |
S |
P |
-- |
|
|
36 |
P |
S |
-- |
|||
|
37 |
When HiRDB is used |
HiRDB log (Including HiRDB definition information) |
-- |
S |
S |
|
|
38 |
HiRDB client log and trace |
-- |
S |
S |
||
|
39 |
Exception log and trace of HiRDB Type4 JDBC driver |
-- |
S |
S |
||
|
40 |
When Oracle is used |
Oracle log |
-- |
S |
S |
|
|
41 |
Oracle JDBC Thin Driver log |
-- |
S |
S |
||
|
42 |
JavaVM output message log |
-- |
S |
S |
||
|
43 |
JavaVM thread dump |
-- |
S |
S |
||
|
44 |
Java VM GC log |
-- |
S |
S |
||
- Legend:
-
P: Primary source. This type of information is used for the primary analysis in the failure investigation.
S: Secondary source. This type of information is required according to the result of the primary analysis.
--: Not required
- #
-
The default directory to which the J2EE server outputs log data is Service-Platform-installation-directory\CC\server\public\ejb\J2EE-server-name\logs. Hereafter, this directory is called the J2EE server's log output directory.
You can change this directory by using the ejb.server.log.directory key in the usrconf.cfg file (option definition file for the J2EE server).