[DERBY-1005] getHoldability does not return CLOSE_CURSORS_AT_COMMIT in a global transaction

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.1.3.1, 10.2.1.6
• Fix Version/s: 10.1.3.1, 10.2.1.6
• Component/s: Network Client
• Assignee: Daniel John Debrunner
• Reporter: Katherine Marsden
• Created: 18/Feb/06 09:44
• Updated: 13/Jul/06 01:04
• Resolved: 25/Apr/06 03:53

Description

Holdability for a connection should automatically become CLOSE_CURSORS_AT_COMMIT for a global transaction.
For client xa Connection.getHoldability returns OLD_CURSORS_OVER_COMMIT within a global transaction.

This issue was discovered when converting checkDataSource30.java to run with client and related code was disabled for client testing.

To reproduce, take out if (TestUtil.isEmbeddedFramework()) for this code in jdbcapi/checkDataSource30.java

if (TestUtil.isEmbeddedFramework())

{ // run only for embedded // Network XA BUG: getHoldability does not return CLOSE_CURSORS_AT_COMMIT for global transaction System.out.println("Notice that connection's holdability at this point is CLOSE_CURSORS_AT_COMMIT because it is part of the global transaction"); System.out.println("CONNECTION(in xa transaction) HOLDABILITY " + (conn1.getHoldability() == ResultSet.HOLD_CURSORS_OVER_COMMIT)); }

Issue Links

• is related to: DERBY-966 creating a preparedStatement outside of a Global tran using a ClientXADatasource will result in an "SqlException: Cannot set holdability" if the statement is used in a Global transaction