If a timeout occurs in a transaction, the KDJE31002-W and KDJE50080-W messages are output. The following information is output in these messages:

KDJE31002-W

• J2EE application name or the class name of the batch application that started the transaction.
• Hash code of the instance and the class name of J2EE component (Enterprise Bean, servlets, or JSPs) that started the transaction
• Maintenance information
• Root application information of the trace based performance analysis

You can confirm the location where the transaction timeout occurred in the trace based performance analysis by matching and confirming the root application information of the trace based performance analysis output to the message with the root application information that is output to the trace based performance analysis file.

You can confirm the trace information before and after the timeout for checking the process contents of the transaction in which a timeout occurred.

KDJE50080-W

• IP address, process ID, and root application information
• Connection ID of the connection that executed the SQL
• Name of the method that executed SQL
• Whether the method that executed SQL is running
• SQL executed last

You can refer to the SQL information that is output in the message, and can investigate the location where the timeout occurred.

For details on messages, see KDJE31002-W and KDJE50080-W in the uCosminexus Application Server Messages.

In the trace based performance analysis file, the trace information is output at the trace collection point immediately before or after the occurrence of timeout in the transaction.

Check the processing contents of the following event IDs.

Table 7-12 Trace based performance analysis that is output when timeout occurs in the transaction