Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 49159 invoked from network); 29 Jun 2005 22:43:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 29 Jun 2005 22:43:15 -0000 Received: (qmail 97297 invoked by uid 500); 29 Jun 2005 22:43:01 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 97180 invoked by uid 500); 29 Jun 2005 22:43:00 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 97129 invoked by uid 99); 29 Jun 2005 22:43:00 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jun 2005 15:43:00 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 3639914 for ; Thu, 30 Jun 2005 00:42:57 +0200 (CEST) Message-ID: <1463272845.1120084977220.JavaMail.jira@ajax.apache.org> Date: Thu, 30 Jun 2005 00:42:57 +0200 (CEST) From: "Kathey Marsden (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Created: (DERBY-414) Client XA has a problem with the TRANSACTION_READ_UNCOMMITTED isolation level Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N 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