In component software, when an error occurs, the status of the software when the error occurs is output to the log as troubleshooting information. Collect and analyze this log and study the cause of error. You can even identify the location of error occurrence from the processing status of the request.

In a system built with the application server, you can collect the log and definition file together in the case of an error in the component software. This information is called snapshot log. The batch collection of a snapshot log is executed automatically, just before the logical server is terminated or the J2EE servers are restarted manually in a batch, in the management domain.

Moreover, when you use CTM, you can specify settings in the J2EE server so that when the J2EE server is terminated abnormally, the error is not returned to the client immediately. CTM locks and controls the scheduling queue of the J2EE application until the J2EE server is restarted. CTM maintains the registered requests and continues to accept requests from clients. As a result, if you restart the J2EE server immediately, you can continue with the operations without causing any trouble that the client might notice. Note that you can use CTM for the component software only with the product including Cosminexus Component Transaction Monitor. For details about the products that you can use, see 2.2.2 Component software functional guide in the manual uCosminexus Application Server Overview.

The following subsections describe the flow of data acquisition and handling when a trouble occurs.

Organization of this section

2.2.1 Overview of Troubleshooting

2.2.2 Flow of data acquisition when a trouble occurs