commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Tarau (JIRA)" <>
Subject [jira] Commented: (DBCP-326) Rollback an uncommited transaction on return
Date Mon, 15 Mar 2010 16:24:27 GMT


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

View raw message