[
https://issues.apache.org/jira/browse/DBCP-567?focusedWorklogId=536168&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-536168
]
ASF GitHub Bot logged work on DBCP-567:
---------------------------------------
Author: ASF GitHub Bot
Created on: 14/Jan/21 21:17
Start Date: 14/Jan/21 21:17
Worklog Time Spent: 10m
Work Description: psteitz commented on pull request #82:
URL: https://github.com/apache/commons-dbcp/pull/82#issuecomment-760481643
Sorry for late response. Changes look good. Better and safer than what I
initially proposed. Thanks.
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 536168)
Time Spent: 1.5h (was: 1h 20m)
> 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
> Fix For: 2.9.0
>
> Time Spent: 1.5h
> 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)
