commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <>
Subject [jira] [Commented] (POOL-305) Add maxAge to pool config
Date Sat, 26 Sep 2015 17:56:04 GMT


Michael Osipov commented on POOL-305:

Hmm..ok, I have will a look again at it when I get back to work on Mon and will tell you my
idea. I would like to stick to the pattern Commons Pool currently applies. A change in approach
would justify Pool 3. Just want to note that we need the feature in regular **and** keyed

> Add maxAge to pool config
> -------------------------
>                 Key: POOL-305
>                 URL:
>             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 [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

View raw message