[DERBY-1325] Isolation level of local connection does not get reset after exiting a global transaction if the isolation level was changed using SQL

• 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: JDBC
• Assignee: Deepa
• Reporter: Deepa
• Created: 13/May/06 06:10
• Updated: 12/Jul/06 02:09
• Resolved: 26/May/06 02:29

Description

If we update the isolation level using SQL instead of JDBC and then join/resume a global transaction, on ending the transaction, the isolation level of the local connection is not restored. The problem seems to be in EmbedXAResource. So it happens with both embedded and client driver. Client driver internally uses SQL to set the transaction isolation. So the problem is more likely to be hit with the client. I will attach a repro and a draft patch with more details.

Issue Links

• is related to: DERBY-1148 Client XA getTransactionIsolation() does not return the correct isolation level when rejoining a global transaction