[ https://issues.apache.org/jira/browse/DBCP-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845659#action_12845659 ]
Adrian Tarau edited comment on DBCP-326 at 3/16/10 2:08 AM: ------------------------------------------------------------ Not a valid request...rollback is performed already. was (Author: adrian.tarau): 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.