When an EJB client using a global transaction is down, recovery of the global transaction is necessary. The recovery of the global transaction can be executed by restarting the EJB client.

The method for confirming whether the global transaction recovery process is complete is described below:

• Execute the cjlisttrn command in Application Server and confirm whether the transaction is in an active state. For details on the cjlisttrn command, see cjlisttrn (Displaying the transaction information of the operating J2EE server) in the uCosminexus Application Server Command Reference Guide.
• Confirm whether the resource adapter can be stopped. If it can be stopped, the recovery process of the global transaction is complete.
• Confirm whether Application Server can be stopped successfully. When it can be stopped successfully, the recovery process of the global transaction is complete.
• Confirm using tools and commands provided by each resource.

Moreover, when multiple EJB clients exist, to examine which EJB client is required for the recovery of global transaction:

1. Confirm the unconcluded transactions by executing the cjlisttrn command by specifying the -pending option.
   

   Execution format

   cjlisttrn server-name -pending -bqual

   Execution example

   cjlisttrn MyServer -pending -bqual

2. From the unconcluded transactions confirmed in procedure 1., confirm whether all the following conditions apply to those transactions:
   
   • Elapsed time increases every time the cjlisttrn command is published
   • Branch type is Sub or Sub(recovered)
   • TmHash value of the KFCB40051-I message output at the time of starting the stopped EJB client is included in the global transaction ID
   The transactions to which all these conditions apply are required for the recovery of global transactions.