Java Transaction Service (JTS) (Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Update 7 Release Notes)

Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Update 7 Release Notes

Java Transaction Service (JTS)

This section describes the known Java Transaction Service (JTS) issues and the associated solutions.

Java Transaction Service Issues

ID	Summary
6218460	Transactions can fail due to a transaction timeout even when the JTS timeout is large enough. Solution Configure the Application Server’s transaction service property, `xaresource-txn-timeout`, and set its value to match the transaction timeout (in seconds) configured for the transaction service.

Summary

6218460

Transactions can fail due to a transaction timeout even when the JTS timeout is large enough.

Solution

Configure the Application Server’s transaction service property, xaresource-txn-timeout, and set its value to match the transaction timeout (in seconds) configured for the transaction service.

Recovery

There are some known problems with the recovery implementations of some of the JDBC drivers. For these known problems, Sun Java System Application Server provided some workarounds. By default, these workarounds will not be used unless you explicitly indicate that these workarounds are to be used.

Issue with the Oracle (R) JDBC driver—Oracle XA Resource implementation’s recover method repeatedly returns the same set of in-doubt Xids regardless of the input flag. According to the XA specs, the Transaction Manager should initially call XAResource.recover with TMSTARTSCAN and then call XAResource.recover with TMNOFLAGS repeatedly until no Xids are returned.

Oracle XA Resource’s commit method also has some problems, which are addressed in a workaround provided by the Application Server. To enable this workaround, the following property should be added to the transaction-service subelement in the server.xml file: oracle-xa-recovery-workaround

This property value should be set to true.
Issue with Sybase JConnect 5.2—There are some known problems with JConnect 5.2 driver which are resolved in JConnect 5.5. If the JConnect 5.2 driver is used, to make recovery to work, the following property should be added to the transaction-service subelement in the server.xml file:

sybase-xa-recovery-workaround

This property value should be sent to true.

Transactions

In the server.xml file, res-type is used to demarcate the connection as non-XA or XA. This demarcation is used to identify the configuration of the data source to drive data. For example, in the Datadirect driver, the same data source can be used as either XA or non-XA.

The default behavior of the data source is non-XA. To make the data source behave as XA with the connpool element for transactions, res-type is needed. For the connpool element to work and participate in transactions, add the following for the attributes res-type in the server.xml file:

res-type="javax.sql.XADataSource"