db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1325) Isolation level of local connection does not get reset after exiting a global transaction if the isolation level was changed using SQL
Date Fri, 12 May 2006 23:27:09 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1325?page=all ]

Deepa Remesh updated DERBY-1325:
--------------------------------

    Attachment: SetIsolation_SQL_JDBC.java
                derby-1325-draft.diff

Attaching a repro 'SetIsolation_SQL_JDBC.java' and a draft patch 'derby-1325-draft.diff' for
the problem. The patch adds a call to update the isolation level in the BrokeredConnection
when joining/resuming a transaction. This is similar to what is done when we start a fresh
transaction. With the patch, I ran the repro and xa suite. This patch is only to get comments/feedback
and not for commit. Please take a look.

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


Mime
View raw message