[
https://issues.apache.org/jira/browse/POOL-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085147#comment-13085147
]
Mark Thomas commented on POOL-99:
---------------------------------
In that scenario, simply execute a validation query (which is good practise
anyway for DB connections which can fail for all sorts of reasons).
> Test for idle time exceeded in borrowObject
> --------------------------------------------
>
> Key: POOL-99
> URL: https://issues.apache.org/jira/browse/POOL-99
> Project: Commons Pool
> Issue Type: Improvement
> Affects Versions: 1.3
> Reporter: Rob Eamon
> Priority: Minor
> Fix For: 2.0
>
>
> For GenericObjectPool, the evictor thread performs a calculation to determine
> if an idle object as "expired." If it has, the object is destroyed.
> Would like borrowObject to perform the same test and destroy behavior.
> I explored using the testOnBorrow facility but the time that the object went
> idle is not available. Only the pool has access to the ObjectTimestampPair
> object that is used to record the time that the object was placed in the
> pool. I explored placing a timestamp in the pooled object and can do that but
> it would seem better if the pool managed that test itself.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
