Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 91967 invoked from network); 16 Nov 2006 09:28:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Nov 2006 09:28:02 -0000 Received: (qmail 47312 invoked by uid 500); 16 Nov 2006 09:28:11 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 47284 invoked by uid 500); 16 Nov 2006 09:28:11 -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: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 47275 invoked by uid 99); 16 Nov 2006 09:28:11 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Nov 2006 01:28:11 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Nov 2006 01:28:00 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 60AE4714326 for ; Thu, 16 Nov 2006 01:27:40 -0800 (PST) Message-ID: <5339773.1163669260393.JavaMail.jira@brutus> Date: Thu, 16 Nov 2006 01:27:40 -0800 (PST) From: "Bernt M. Johnsen (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-638) Network driver setTransactionIsolation() causes a commit, but does not complete it locally In-Reply-To: <308453680.1129919732110.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ http://issues.apache.org/jira/browse/DERBY-638?page=all ] Bernt M. Johnsen updated DERBY-638: ----------------------------------- Fix Version/s: 10.3.0.0 > Network driver setTransactionIsolation() causes a commit, but does not complete it locally > ------------------------------------------------------------------------------------------ > > Key: DERBY-638 > URL: http://issues.apache.org/jira/browse/DERBY-638 > Project: Derby > Issue Type: Bug > Components: Network Client > Affects Versions: 10.2.1.6, 10.1.3.1, 10.3.0.0 > Reporter: Deepa Remesh > Assigned To: Bernt M. Johnsen > Fix For: 10.2.1.8, 10.3.0.0 > > Attachments: d638.java, d638_repro2.java, d638_repro3.java, DERBY-638-v2.diff, DERBY-638-v3.diff, DERBY-638-v3.stat, DERBY-638.diff > > > When autocommit is set to false, a call to setTransactionIsolation using client driver does not end the transaction when the method exits. When a close() is called on the conection, it throws an exception. > Running the code below: > conn.setAutoCommit(false); > conn.setTransactionIsolation(Connection.TRANSACTION_READ_COMMITTED); > try{ > conn.close(); > }catch(SQLException se){ > System.out.println("Got exception when closing the connection"); > se.printStackTrace(); > } > with client driver gives: > Got exception when closing the connection > org.apache.derby.client.am.SqlException: java.sql.Connection.close() requested while a transaction is in progress on the connection.The transaction remains active, and the connection cannot be closed. > with embedded driver, it works okay and does not throw any exception. -- 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