[
https://issues.apache.org/jira/browse/DBCP-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845396#action_12845396
]
Adrian Tarau commented on DBCP-326:
-----------------------------------
Hmm, not really but this is the only explanation that I could find for
something that happened a few weeks ago.
Is this included in 1.2.x also? We used 1.2.2 until recently and honestly I'm
not sure if it was 1.2.x or 1.3.x when it happened :)
> 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.3, 1.4
> 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.
