[ https://issues.apache.org/jira/browse/POOL-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Steitz updated POOL-305: ----------------------------- Fix Version/s: 3.0 > 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 > Priority: Major > Fix For: 3.0 > > > 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|https://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html]. > 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 (v8.20.10#820010)