db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-414) Client XA has a problem with the TRANSACTION_READ_UNCOMMITTED isolation level
Date Wed, 29 Jun 2005 22:42:57 GMT
Client XA has a problem with the TRANSACTION_READ_UNCOMMITTED isolation level
-----------------------------------------------------------------------------

         Key: DERBY-414
         URL: http://issues.apache.org/jira/browse/DERBY-414
     Project: Derby
        Type: Bug
  Components: Network Client  
    Versions: 10.1.1.0, 10.2.0.0    
    Reporter: Kathey Marsden
 Attachments: deby414Repro.zip


When using v10.1.1.0 of the Apache Derby Network Client JDBC Driver and configuring
the TRANSACTION_READ_UNCOMMITTED isolation level, it is unable to read changes from another
transaction which haven't been committed yet. 

$ java TestDerbyNSXA
Connection number: 2.
Database product: Apache Derby
Database version: 10.2.0.0 alpha
Driver name:      Apache Derby Network Client JDBC Driver
Driver version:   10.2.0.0 alpha
Thread 1: transaction started (with read committed isolation)
Thread 1: row updated first time.
Connection number: 3.
Thread 2: transaction started (with read uncommitted isolation)
Query complete on thread 2. About to do ResultSet.next()...
Thread 1: row updated second time.
ResultSet.next() took 19067 milliseconds.
Test fails. ResultSet next under read uncommitted isolation appears to have been blocked and
unable to perform a dirty read.
Thread 1: transaction committed.
Thread 2: transaction committed.
$


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