Hitachi

uCosminexus Application Server Expansion Guide


9.5.2 Troubleshooting in the event of an error in CTM

If a value in the range from 1213473793 to 1213474042 is set as the minor code in a CORBA system exception, you can determine the cause of the error that occurred in CTM from the exception log file output to the CTMSPOOL directory.

Organization of this subsection

(1) Format of the exception log file

The exception log will store information obtained each time an error occurs. Each record that is stored is a comma-separated list consisting of 17 fields.

Field

Item obtained

Explanation

1

Time

Error occurrence time

2

Process

Process ID

3

Thread

Thread ID

4

ClientIPAddress

IP address of the ORB client

5

ClientPortNo

Port number of the ORB client

6

ClientCommNo

Communication number

7

ErrorCode

Error code

8

DetailCode

Detail code

9

PlaceCode

Place code

10

CompletionStatus

Completion status

11

MaintenanceCode1

Maintenance information

12

MaintenanceCode2

Maintenance information

13

MaintenanceCode3

Maintenance information

14

MaintenanceCode2

Maintenance information

15

ErrorCode

Error code returned to the ORB client

16

CompletionStatus

Completion status returned to the ORB client

17

MinorCode

Minor code returned to the ORB client

The following figure shows an example of data output to the exception log.

Figure 9‒11: Example of data output to the exception log

[Figure]

(2) Troubleshooting procedure

  1. In the exception log file, check whether minor codes received by the ORB client have been output to field 17.

    The location of the exception log file is as follows:

    In Windows:

    CTMSPOOL-directory\ejb\CTMID-name-of-connection-destination\expt\

    In UNIX:

    CTMSPOOL-directory/ejb/CTMID-name-of-connection-destination/expt/

  2. If minor codes have been output, find the one on the line where the error occurrence time (field 1) is the same as the time when the error occurred. Then, confirm that the IP address (field 4) and port number (field 5) are the same as those for the ORB client.

  3. On the line you found, check the error code (field 7), detail code (field 8), place code (field 9), and completion status (field 10). Then, by referring to 19.4 Details of KFCT messages in the manual uCosminexus Application Server Messages, take appropriate action based on the information you checked.

  4. On the line you found, check the communication number (field 6). Then, use the PRF trace to find the last point at which the request was processed to narrow down the location where the problem occurred.