This subsection describes the notes on operations when transactions are started with the EJB client applications.

• After you stop the EJB client application, if you cannot stop Application Server and resource adapter, the unconcluded transactions might remain in the transaction. In this case, restart the EJB client application and recover the global transaction.
  Note that the recovery processing is executed by invoking service initialization in the EJB client application after the application is restarted.
  
• If the EJB client computer is down due to reasons such as errors during transaction processing, you must restart the EJB client application and then recover the global transaction.
• The transactions started with the EJB client applications cannot be forcefully concluded by using the method cancellation functionality.
• If an exception occurs during service initialization, the items such as the system properties for executing the EJB client applications might be specified incorrectly. Take action according to the exception message.
• When transactions are started with the EJB client applications, the root application information and client application information is not included in the trace based performance analysis output by the JTA and OTS. To trace a request, use the hash code and the XID information of the thread.
  Also, the message output when a transaction timeout occurs includes the hash code of the thread that started the transaction, instead of the root application information. You can also use this information to trace a request.