[DERBY-1006] Client allows setHoldability to HOLD_CURSORS_OVER_COMMIT on both connection and statement in a global transaction

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.1.3.1, 10.3.1.4
• 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:51
• Updated: 01/Jul/06 08:15
• Resolved: 25/Apr/06 03:53

Description

Client allows holdability to be set to HOLD_CURSORS_OVER_COMMIT in a global transaction.
I am not sure of the impact on the server side.

To reproduce look for this code in checkDataSource30 and take out the return for client.

if (!TestUtil.isEmbeddedFramework())

{ // Don't run the rest of the test for client // Network XA BUG: Client allows set HOLD_CURSORS_OVER_COMMIT // to be set in a a global transaction on the connection and // statements conn.close(); return; }

xid = getXid(24, (byte) 21, (byte) 01);
xr.start(xid, XAResource.TMNOFLAGS);
System.out.println("CONNECTION(xa) HOLDABILITY " + (conn.getHoldability() == ResultSet.HOLD_CURSORS_OVER_COMMIT));
try

{ conn.setHoldability(ResultSet.HOLD_CURSORS_OVER_COMMIT); System.out.println("FAIL allowed to set hold mode in xa transaction"); }

catch (SQLException sqle)

{ System.out.println("Expected SQLException(setHoldability) " + sqle.getMessage()); }