Database Reference
In-Depth Information
An exception occurred during transaction completion: nested exception is javax.transaction.RollbackException: Timed out
Or
oracle.fabric.common.FabricInvocationException: org.springframework.transaction.UnexpectedRollbackException:JTA transaction unexpectedly rolled back (maybe due to a timeout) Transaction timed out after 31 seconds
There are primarily four types of timeout parameters which are responsible for
the majority of timeout errors. Tuning the transaction timeout parameters cor-
rectly will take care of most of the troublesome timeout issues. These timeout
parameters can be tuned at the:
•
Application server level
•
EJB level
•
Component engine level
•
HTTP level (discussed later under the
Tuning Composite Application
section)
Tuning transactions at the application server level
In this section, you will see a short list of recommendations to help you optimize
your application's ability to manage transactions and timeouts optimally. These
tuning techniques are applicable to nearly all application servers that we may
use, but for the scope of this topic, we will limit ourselves to Oracle WebLogic
Server.
Tuning Java Transaction API (JTA)
Oracle WebLogic Server's EJB container includes a global transaction handling
mechanism that provides begin/commit/rollback functionality for applications
that need to explicitly demarcate transaction boundaries.
The following diagram shows how Oracle WebLogic Server internally handles
transactions between different transactional as well as non-transactional applic-
ations. Clients may participate in a transaction by handling over the commit and
rollback responsibility to the server's EJB Container that contains a deployment
descriptor to automatically manage transactions. The global transaction object
