Isolation level of local connection does not get reset after exiting a global
transaction if the isolation level was changed using SQL
---------------------------------------------------------------------------------------------------------------------------------------
Key: DERBY-1325
URL: http://issues.apache.org/jira/browse/DERBY-1325
Project: Derby
Type: Bug
Components: JDBC
Versions: 10.2.0.0, 10.1.3.0
Reporter: Deepa Remesh
Assigned to: Deepa Remesh
Fix For: 10.2.0.0, 10.1.3.0
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
