Database Reference
In-Depth Information
provides objects' simple begin/suspend/resume functionalities for applications
that need to explicitly demarcate transactional boundaries.
Transactions enlisted in JTA are subject to timeouts. The JTA transaction
timeout errors can be identified by the following error found in the engine logs:
Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 301 seconds
The default maximum time that an instance can be enlisted in a transaction is
30 seconds. The above error is likely due to the fact that a particular transaction
took more time than the maximum time specified.
Tuning of the JTA is of utmost importance for one or all of the following reasons:
•
Automatic activities, such as service tasks and invokes in BPMN or BPEL
processes, may overshoot the minimum timeout threshold
•
High concurrency may lead to low performance databases, queuing sys-
tems, and/or external endpoints that may keep the transactions alive for
more than the specified timeout setting
•
Improper transaction handling in the design of composite applications that
may accidentally lead to long running transactions without a proper dehydra-
tion
To tune the underlying Oracle WebLogic Server's JTA, log in to the Oracle We-
bLogic Server Administration Console. From the landing page, navigate to
Ser-
