[jira] [Comment Edited] (DBCP-491) Ensure DBCP ConnectionListener can deal with transaction managers which invoke rollback in a separate thread

["Gary Gregory (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DBCP-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16494168#comment-16494168 ] 

Gary Gregory edited comment on DBCP-491 at 5/29/18 8:02 PM:
------------------------------------------------------------

If I run the unit test {{testConnectionInTimeout}} without the main code changes, it passes. Should it not fail? The other tests fail, which I expected.


was (Author: garydgregory):
If I run the unit test {{testConnectionInTimeout}} without the main code changes, it passes. Should it not fail?

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