[DERBY-1148] Client XA getTransactionIsolation() does not return the correct isolation level when rejoining a global transaction

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.2.1.6
• Fix Version/s: 10.1.3.1, 10.2.1.6
• Component/s: Network Client
• Assignee: Deepa
• Reporter: Katherine Marsden
• Created: 24/Mar/06 09:44
• Updated: 14/Nov/06 13:27
• Resolved: 02/Jun/06 23:26

Description

When rejoining a global transaction, client does not report the correct isolation level with a
getTransactionIsolation(). The server side isolation should be ok I think.

This was discovered when testing the fix for DERBY-1044. After the fix for DERBY-1044, there is a new diff in the test, but the fix for DERBY-1044 just exposed this issue. The output for the test was correct before by circumstance.

I will put comments with this bug in checkDataSource test.

// now re-join the transaction, should pick up the read-only
// and isolation level from the transaction,
// holdability remains that of this handle.
xar.start(xid, XAResource.TMJOIN);
printState("re-join X1", cs1);
xar.end(xid, XAResource.TMSUCCESS);

Issue Links

• incorporates: DERBY-1035 With client, Connection.getTransactionIsolation() return value is wrong after changing the isolation level with an SQL statement such as "set current isolation = RS"
• is related to: DERBY-2084 getTransactionIsolation() in network client should not activate a transaction
• relates to: DERBY-1325 Isolation level of local connection does not get reset after exiting a global transaction if the isolation level was changed using SQL