[
https://issues.apache.org/jira/browse/POOL-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14909233#comment-14909233
]
Michael Osipov commented on POOL-305:
-------------------------------------
Hi Phil, I am able to commit the stuff myself after your review.
Looking at the source code, tells me that I have to modify {{EvictionConfig}}
and the {{DefaultEvictionPolicy}} which will in turn tell whether this pooled
object has reached its maximum age. Does my approach sound right?
> 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)
