Workaroundsfor Specic Databases

TheEnterprise Server provides workarounds for some known issues with the recovery
implementationsof the following JDBC drivers. These workarounds are used unless explicitly
disabled.
■Oraclethin driver - The XAResource.recover method repeatedly returns the same set of
in-doubtXids regardless of the input ag. According to the XA specications, the
TransactionManager initially calls this method with TMSTARTSCAN and then with
TMNOFLAGSrepeatedly until no Xids are returned. The XAResource.commit method also
hassome issues.
Todisable the Enterprise Server workaround, set the oracle-xa-recovery-workaround
propertyvalue to false. For details about how to set a property, see “To congure how the
EnterpriseServer recovers from transactions” on page 145.
Note– These workarounds do not imply support for any particular JDBC driver.
AdminConsole Tasks for Transactions
TheEnterprise Server handles transactions based on the settings in the Admin Console.

ConguringTransactions

Thissection explains how to congure transaction settings:
■“Tocongure how the Enterprise Server recovers from transactions” on page 145
■“Toset a transaction timeout value” on page 146
■“Toset the location of the transaction logs” on page 147
■“Toset the keypoint interval” on page 148
Foradditional information about transactions, see these sections:
■“Whatis a Transaction?” on page 143
■“Transactionsin Java EE Technology” on page 144

▼Tocongure how the Enterprise Server recoversfrom transactions

Transactionsmight 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.
EnterpriseServer is designed to recover from these failures and complete the transactions upon
serverstartup.
Whileperforming the recovery, if some of the resources are unreachable the server restart may
bedelayed as it tries to recover the transactions.
AdminConsoleTasks for Transactions
Chapter12 • Transactions 145