You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2018/05/29 21:07:00 UTC
[jira] [Resolved] (DBCP-491) Ensure DBCP ConnectionListener can
deal with transaction managers which invoke rollback in a separate thread
[ https://issues.apache.org/jira/browse/DBCP-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Gregory resolved DBCP-491.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.3.1
I applied a modified version of [~zhfeng]'s patch. Please verify and close this ticket and associated PR if it works for you. More unit tests would also be welcome to any area.
> Ensure DBCP ConnectionListener can deal with transaction managers which invoke rollback in a separate thread
> ------------------------------------------------------------------------------------------------------------
>
> Key: DBCP-491
> URL: https://issues.apache.org/jira/browse/DBCP-491
> Project: Commons DBCP
> Issue Type: Bug
> Affects Versions: 2.3.0
> Reporter: Zheng Feng
> Priority: Major
> Fix For: 2.3.1
>
>
> By using the ManagedDataSource with the [Narayana|http://narayana.io], the CompletionListener in DBCP is resetting too much of the state of the connection in afterCompletion when it should be waiting until the connection is also closed by the user.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)