From issues-return-12690-apmail-commons-issues-archive=commons.apache.org@commons.apache.org Sun Mar 14 03:03:33 2010 Return-Path: Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: (qmail 8435 invoked from network); 14 Mar 2010 03:03:32 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 14 Mar 2010 03:03:32 -0000 Received: (qmail 8618 invoked by uid 500); 14 Mar 2010 03:02:50 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 8532 invoked by uid 500); 14 Mar 2010 03:02:50 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 8520 invoked by uid 99); 14 Mar 2010 03:02:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Mar 2010 03:02:50 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Mar 2010 03:02:48 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 3AF7A234C052 for ; Sun, 14 Mar 2010 03:02:27 +0000 (UTC) Message-ID: <781642650.251231268535747240.JavaMail.jira@brutus.apache.org> Date: Sun, 14 Mar 2010 03:02:27 +0000 (UTC) From: "Adrian Tarau (JIRA)" To: issues@commons.apache.org Subject: [jira] Created: (DBCP-326) Rollback an uncommited transaction on return MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org Rollback an uncommited transaction on return -------------------------------------------- Key: DBCP-326 URL: https://issues.apache.org/jira/browse/DBCP-326 Project: Commons Dbcp Issue Type: Improvement Affects Versions: 1.4, 1.3 Environment: Any Reporter: Adrian Tarau Priority: Critical DBCP should perform a rollback(should be configurable but by default activated) when the datasource has auto-commit=false. The reason behind is to avoid passing a partial transaction to the next client. Rolling back a transaction(in case it wasn't committed of course) adds a guarantee to the validity of a connection borrowed from the pool. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.