[DBCP-534] Allow for manual connection eviction

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.5.0
• Fix Version/s: 2.6.0
• Assignee: Unassigned
• Reporter: Peter Wicks
• Created: 10/Jan/19 15:20
• Updated: 27/Oct/21 00:15
• Resolved: 27/Oct/21 00:15

Description

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.

Issue Links

• links to: GitHub Pull Request #29