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 Thu, 18 May 2006 20:00:06 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1325?page=all ]

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

    Attachment: derby-1325-v2.diff
                derby-1325-v2.status

Thanks Kathey and Mamta for looking at the patch. I am attaching an updated patch 'derby-1325-v2.diff'
because the first patch became outdated after the commit for DERBY-1219. In the new patch,
I moved the test into a new method in checkDataSource.java. I verified the test fails without
the patch and passes with the patch. Please review/commit this patch.

> 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


Mime
View raw message