Return-Path: Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: (qmail 9194 invoked from network); 28 Mar 2009 13:44:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 28 Mar 2009 13:44:15 -0000 Received: (qmail 86773 invoked by uid 500); 28 Mar 2009 13:44:14 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 86651 invoked by uid 500); 28 Mar 2009 13:44:14 -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 86641 invoked by uid 99); 28 Mar 2009 13:44:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 Mar 2009 13:44:14 +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; Sat, 28 Mar 2009 13:44:12 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 7C12A234C003 for ; Sat, 28 Mar 2009 06:43:50 -0700 (PDT) Message-ID: <855957302.1238247830500.JavaMail.jira@brutus> Date: Sat, 28 Mar 2009 06:43:50 -0700 (PDT) From: "Phil Steitz (JIRA)" To: issues@commons.apache.org Subject: [jira] Commented: (DBCP-286) MAJOR, MAJOR, MAJOR dbcp does not rollback In-Reply-To: <61518374.1238193290828.JavaMail.jira@brutus> 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 [ https://issues.apache.org/jira/browse/DBCP-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693437#action_12693437 ] Phil Steitz commented on DBCP-286: ---------------------------------- Can you provide some more information on your environment and what exactly you are observing? Specifically - autocommit, readonly (when connection is returned and default values), testOnBorrow, testOnReturn, pool version, jdbc driver. I assume that what you are seeing is when a connection is returned with readonly=false, automcommit=false, no rollback is happening in 1.2.2. Correct? > MAJOR, MAJOR, MAJOR dbcp does not rollback > ------------------------------------------ > > Key: DBCP-286 > URL: https://issues.apache.org/jira/browse/DBCP-286 > Project: Commons Dbcp > Issue Type: Bug > Affects Versions: 1.2.2 > Environment: maven, gentoo linux, any java version > Reporter: Trenton D. Adams > Priority: Blocker > Original Estimate: 1h > Remaining Estimate: 1h > > DBCP 1.2.2 does not do connection rollbacks. Or, at least the one in maven 2 repositories does not. I switched back to 1.2.1, and it works great. > I asked about this back in 2005, and it was stated that it did. And, it does, up until 1.2.2 > http://mail-archives.apache.org/mod_mbox/commons-user/200504.mbox/<425CB254.1020504@pandora.be> -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.