[
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.1020...@pandora.be>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
