You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Zheng Feng (JIRA)" <ji...@apache.org> on 2018/06/03 15:53:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16499459#comment-16499459 ] 

Zheng Feng commented on DBCP-491:
---------------------------------

Thanks [~garydgregory], it works for me.

> 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)