[
https://issues.apache.org/jira/browse/DBCP-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434617#comment-17434617
]
Peter Wicks commented on DBCP-534:
----------------------------------
[~ggregory] I think this can be closed. The PR was merged a long time ago.
> 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
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)
