commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (POOL-305) Add maxAge to pool config
Date Fri, 25 Sep 2015 16:37:04 GMT

    [ https://issues.apache.org/jira/browse/POOL-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908288#comment-14908288
] 

Phil Steitz commented on POOL-305:
----------------------------------

Good idea.  Patches welcome!

> Add maxAge to pool config
> -------------------------
>
>                 Key: POOL-305
>                 URL: https://issues.apache.org/jira/browse/POOL-305
>             Project: Commons Pool
>          Issue Type: Improvement
>    Affects Versions: 2.4.2
>            Reporter: Michael Osipov
>
> In our environment, there are upper caps to session lifetime regardless how often the
session has been busy/idle. Given that an object in a pool can remain for an indefinite time
as long as it is used often enough, it may also already be invalided by the server.
> To avoid such issues, I'd like to have a {{maxAge}} property for an object, where eviction
kicks in by default. This is the very same as in the [https://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html|Tomcat
JDBC Connection Pool].
> I am quite certain that this is possible with a custom eviction policy but I do think
that should be available by default.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message