You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/01/13 19:07:00 UTC

[jira] [Work logged] (DBCP-567) Use abort rather than close to clean up abandoned connections

     [ https://issues.apache.org/jira/browse/DBCP-567?focusedWorklogId=535633&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-535633 ]

ASF GitHub Bot logged work on DBCP-567:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 13/Jan/21 19:06
            Start Date: 13/Jan/21 19:06
    Worklog Time Spent: 10m 
      Work Description: garydgregory merged pull request #82:
URL: https://github.com/apache/commons-dbcp/pull/82


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 535633)
    Time Spent: 1h 20m  (was: 1h 10m)

> Use abort rather than close to clean up abandoned connections
> -------------------------------------------------------------
>
>                 Key: DBCP-567
>                 URL: https://issues.apache.org/jira/browse/DBCP-567
>             Project: Commons DBCP
>          Issue Type: Improvement
>            Reporter: Phil Steitz
>            Priority: Minor
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Using abort rather than close to disconnect abandoned connections will make it less likely that pool threads get stuck waiting for locks on abandoned connections.
> To implement this, we will need the changes inĀ [Pool 387|https://issues.apache.org/jira/browse/POOL-387]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)