[jira] [Work logged] (DBCP-534) Allow for manual connection eviction

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[jira] [Work logged] (DBCP-534) Allow for manual connection eviction

JIRA jira@apache.org

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

ASF GitHub Bot logged work on DBCP-534:

                Author: ASF GitHub Bot
            Created on: 16/Jan/19 11:38
            Start Date: 16/Jan/19 11:38
    Worklog Time Spent: 10m
      Work Description: chtompki commented on issue #29: DBCP-534 Allow for manual connection eviction
URL: https://github.com/apache/commons-dbcp/pull/29#issuecomment-454748606
   No worries :-)
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[hidden email]

Issue Time Tracking

    Worklog Id:     (was: 185710)
    Time Spent: 0.5h  (was: 20m)

> 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