[DBCP-491] Ensure DBCP ConnectionListener can deal with transaction managers which invoke rollback in a separate thread

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.3.0
• Fix Version/s: 2.4.0
• External issue URL: https://github.com/apache/commons-dbcp/pull/12
• External issue ID: 12
• Assignee: Unassigned
• Reporter: Zheng Feng
• Created: 17/May/18 05:24
• Updated: 03/Jun/18 15:52
• Resolved: 29/May/18 21:06

Description

By using the ManagedDataSource with the Narayana, 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.

Issue Links

• is related to: DBCP-484 Connection leak during XATransaction in high load