[jira] [Resolved] (DBCP-516) Do not double returnObject back to the pool if there is a transaction context with a shared connection

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

     [ https://issues.apache.org/jira/browse/DBCP-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Gregory resolved DBCP-516.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 2.6.0

[~tomjenkinson],

Thank you for your patch!

I applied a revised version of the patch.

Please verify and close this ticket.

Gary

> Do not double returnObject back to the pool if there is a transaction context with a shared connection
> ------------------------------------------------------------------------------------------------------
>
>                 Key: DBCP-516
>                 URL: https://issues.apache.org/jira/browse/DBCP-516
>             Project: Commons DBCP
>          Issue Type: Bug
>            Reporter: Tom Jenkinson
>            Priority: Major
>             Fix For: 2.6.0
>
>
> It is possible for the same thread to return a connection to the pool twice:
> {code:java}
> // in TX
> c = getConnection()
> // in aftercompletion
> c.getWarnings()
> c.getWarnings(){code}
> This issue was uncovered after resolving DBCP-515.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)