Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Message-ID: <2111037426.1128013309329.JavaMail.jira@ajax.apache.org>
Date: Thu, 29 Sep 2005 19:01:49 +0200 (CEST)
From: "Deepa Remesh (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-414) With Network Client starting an XA
 transaction resets the isolation level set with setTransactionIsolation
In-Reply-To: <1463272845.1120084977220.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-414?page=all ]

Deepa Remesh updated DERBY-414:
-------------------------------

    Fix Version: 10.1.1.1

> With Network Client starting an XA transaction resets the isolation level set with setTransactionIsolation
> ----------------------------------------------------------------------------------------------------------
>
>          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
>     Assignee: Mamta A. Satoor
>      Fix For: 10.2.0.0, 10.1.2.0, 10.1.1.1
>  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 if the setTransactionIsolation call comes before the xa transation is started.
> $ 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