[ http://issues.apache.org/jira/browse/DERBY-1325?page=comments#action_12412985 ]
Kathey Marsden commented on DERBY-1325: --------------------------------------- Comitted to the trunk. Won't mark resolved until it goes into 10.1 Date: Tue May 23 13:29:47 2006 New Revision: 409002 URL: http://svn.apache.org/viewvc?rev=409002&view=rev Thanks Deepa! > 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 > Assignee: Deepa Remesh > Fix For: 10.2.0.0, 10.1.3.0 > Attachments: SetIsolation_SQL_JDBC.java, derby-1325-draft.diff, > derby-1325-v1.diff, derby-1325-v1.status, derby-1325-v2.diff, > derby-1325-v2.status > > 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
