Database Reference
In-Depth Information
A general rule to follow is to make sure that the Oracle
WebLogic Server JTA timeout is set to a lower value than
the shortest timeout value configured for a participating
XA resource (for example, XA Transaction Timeout
for Oracle XA JDBC connections). Not doing so can lead
to an unexpected and inconsistent distributed transaction
outcome, that is, a participating XA Resource timing out
before Oracle WebLogic Server JTA as the distributed
transaction coordinator. The timed out XA Resource may
take action to resolve its own part of the distributed trans-
action before Oracle WebLogic Server can take action.
This will lead to heuristic error messages at the time when
the Oracle WebLogic Server transaction manager tries to
prepare/commit the distributed transaction.
Tuning EJB timeouts for long running transactions
Oracle SOA Suite 11g contains an Enterprise Java Bean (EJB) set that forms
a part of the SOA Infra ( soa-infra ) application in the Oracle WebLogic Server.
Each of these EJB objects has a pre-defined timeout setting that overrides the
one set at the infrastructure. By default, this is set to 300 seconds . Timeout
errors could occur in the case of long running processes slowing down the over-
all SOA system. The following EJBs will, therefore, have to be tuned in order to
participate in global transactions and avoid timeouts:
BPELActivityManagerBean
BPELDeliveryBean
BPELDispatcherBean
BPELEngineBean
BPELFinderBean
Search WWH ::




Custom Search