Workarounds For Specific Databases; Admin Console Tasks For Transactions; Configuring Transactions - Sun Microsystems GlassFish Enterprise Server 2.1 Administration Manual

Workarounds for Specific Databases

The Enterprise Server provides workarounds for some known issues with the recovery
implementations of the following JDBC drivers. These workarounds are used unless explicitly
disabled.
■
Note –

Admin Console Tasks for Transactions

The Enterprise Server handles transactions based on the settings in the Admin Console.

Configuring Transactions

This section explains how to configure transaction settings:
"To configure how the Enterprise Server recovers from transactions" on page 145
■
"To set a transaction timeout value" on page 146
■
"To set the location of the transaction logs" on page 147
■
"To set the keypoint interval" on page 148
■
For additional information about transactions, see these sections:
"What is a Transaction?" on page 143
■
"Transactions in Java EE Technology" on page 144
■
▼
To configure how the Enterprise Server recovers from transactions
Transactions might be incomplete either because the server crashed or a resource manager
crashed. It is essential to complete these stranded transactions and recover from the failures.
Enterprise Server is designed to recover from these failures and complete the transactions upon
server startup.
While performing the recovery, if some of the resources are unreachable the server restart may
be delayed as it tries to recover the transactions.
Chapter 12 • Transactions
Oracle thin driver - The XAResource.recover method repeatedly returns the same set of
in-doubt Xids regardless of the input flag. According to the XA specifications, the
Transaction Manager initially calls this method with TMSTARTSCAN and then with
TMNOFLAGS repeatedly until no Xids are returned. The XAResource.commit method also
has some issues.
To disable the Enterprise Server workaround, set the oracle-xa-recovery-workaround
property value to false. For details about how to set a property, see
Enterprise Server recovers from transactions" on page
These workarounds do not imply support for any particular JDBC driver.
Admin Console Tasks for Transactions
"To configure how the
145.
145