You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2019/01/10 19:46:00 UTC
[jira] [Commented] (DBCP-534) Allow for manual connection eviction
[ https://issues.apache.org/jira/browse/DBCP-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739721#comment-16739721 ]
Gary Gregory commented on DBCP-534:
-----------------------------------
Please feel free to propose a patch with unit tests on GitHub ;-)
> Allow for manual connection eviction
> ------------------------------------
>
> Key: DBCP-534
> URL: https://issues.apache.org/jira/browse/DBCP-534
> Project: Commons DBCP
> Issue Type: Improvement
> Affects Versions: 2.5.0
> Reporter: Peter Wicks
> Priority: Minor
>
> Currently the pool only allows you to either immediately evict connections based on min/max values, or evict them when a thread wakes up and kills them.
> The underlying `GenericObjectPool` supports evicting connections immediately without waiting on a schedule. This would support scenarios where a developer may want to keep a large pool of idle connections available for a period of time, but then wants to immediately evict them after a certain part of a program has completed without waiting for a delay.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)