commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Gregory (JIRA)" <>
Subject [jira] [Commented] (POOL-305) Add maxAge to pool config
Date Sat, 26 May 2018 17:19:00 GMT


Gary Gregory commented on POOL-305:

Is this issue still alive?

> Add maxAge to pool config
> -------------------------
>                 Key: POOL-305
>                 URL:
>             Project: Commons Pool
>          Issue Type: Improvement
>    Affects Versions: 2.4.2
>            Reporter: Michael Osipov
>            Priority: Major
> 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