Client XA getTransactionIsolation() does not return the correct isolation level when rejoining a global transaction

• Key: DERBY-1148
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Major
• Assignee: Deepa Remesh
• Reporter: Kathey Marsden
• Component/s: Network Client
• Affects Version/s: 10.2.1.6
• Fix Version/s: 10.1.3.1, 10.2.1.6

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);