You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Adrian Tarau (JIRA)" <ji...@apache.org> on 2010/03/16 03:08:27 UTC
[jira] Closed: (DBCP-326) Rollback an uncommited transaction on
return
[ https://issues.apache.org/jira/browse/DBCP-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrian Tarau closed DBCP-326.
-----------------------------
Resolution: Invalid
Not a valid request...
> 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.