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 Mon, 15 May 2006 16:04:07 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1325?page=all ]

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

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

Attaching a patch 'derby-1325-v1.diff' which ensures correct isolation level gets used once
we switch back to local mode when SQL is used to set the isolation level.

Patch does the following:

* Adds call to get the isolation level up to date when joining/resuming a global transaction.
This will make sure the BrokeredConnection object has the correct isolation level to be used
when we switch back to local mode.

* Adds a test to jdbcapi/checkDataSource.java and modifies the master files.

With this patch, I ran derbyall with Sun jdk 1.4.2 on Windows XP. No failures. I would appreciate
if someone can take a look at 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
>
> 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