You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Tom Jenkinson (JIRA)" <ji...@apache.org> on 2018/07/26 07:45:00 UTC

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

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

Tom Jenkinson commented on DBCP-516:
------------------------------------

Thanks, the changes look good to me!

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