5.5.4 Forced termination process
In the forced termination process, the lock process and stop process are not executed for the normal termination. The process is cancelled forcibly even when there is a request that is being processed in the J2EE application. Note that a method being executed is cancelled.
- Handling the transaction when a J2EE application is terminated forcibly
-
When a J2EE application is forcibly terminated, the transaction that is about to be performed is timed out forcibly. As a result, an exception occurs and the transaction cannot be started if you try to start the transaction after the J2EE application is terminated forcibly.
However, when the in-process OTS is running across multiple JavaVM, the transaction is not timed out forcibly even when the J2EE application is terminated forcibly.
Furthermore, if an SQL statement is being executed in Statement, CallableStatement, or PreparedStatement when the J2EE application is terminated forcibly, the execution is cancelled and the control tends to return to the J2EE application. The connection used in the J2EE application is destroyed and does not return to the pool.
For details on the transaction timeout, see 3.15.8 Transaction timeout and statement cancellation in the uCosminexus Application Server Common Container Functionality Guide.