Enables WebLogic Server to keep the logical JDBC connection open
for a global transaction when the physical XA connection is
returned to the connection pool.

Select this option if the XA driver used to create database
connections or the DBMS requires that a logical JDBC connection be
kept open while transaction processing continues (although the
physical XA connection can be returned to the connection pool).

Only applies to data sources that use an XA driver.

Use this setting to work around specific problems with JDBC XA
drivers.

Specifies whether the XA driver requires a distributed
transaction context when closing various JDBC objects (result sets,
statements, connections, and so forth). Only applies to connection
pools that use an XA driver.

When enabled, SQL exceptions that are thrown while closing the
JDBC objects without a transaction context will be suppressed.

Use this setting to work around specific problems with JDBC XA
drivers.

Enables JTA resource health monitoring for an XA data source.
When enabled, if an XA resource fails to respond to an XA call
within the period specified in MaxXACallMillis, WebLogic Server
marks the data source as unhealthy and blocks any further calls to
the resource.

This property applies to XA data sources only, and is ignored
for data sources that use a non-XA driver.

Enables WebLogic Server to set a transaction branch timeout
based on the value for XaTransactionTimeout.

When enabled, the WebLogic Server Transaction Manager calls
XAResource.setTransactionTimeout() before calling
XAResource.start, and passes either the XA Transaction
Timeout value or the global transaction timeout.

You may want to set a transaction branch timeout if you have
long-running transactions that exceed the default timeout value on
the XA resource.

Note: To use this feature, the resource manager
(typically, the JDBC driver) must support the
javax.transaction.xa.XAResource.setTransactionTimeout()
method.