commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <>
Subject [jira] Commented: (DBCP-286) MAJOR, MAJOR, MAJOR dbcp does not rollback
Date Sat, 28 Mar 2009 13:43:50 GMT


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:
>             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

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message