Number of tested objects in eviction runs of GenericKeyedObjectPool
-------------------------------------------------------------------
Key: POOL-145
URL: https://issues.apache.org/jira/browse/POOL-145
Project: Commons Pool
Issue Type: Bug
Affects Versions: 1.5.1
Environment: Operating System: All
Platform: All
Reporter: Klaus Kopruch
Priority: Minor
Hi,
if numTestsPerEvictionRun is set to n and there are less than n idle objects in
the pool, the evictor thread will still make n tests on these objects in a
round-robin manner, i.e. idle objects can be tested more than once per eviction
run. As this also includes validity tests if testWhileIdle is enbabled and
validity tests may be time-consuming, this is a rather unwanted behavior.
Instead of testing getNumTests() objects, the pool should test
min(_pool.size(),getNumTests()) objects per eviction run.
[[email protected]] already reported this bug for GenericObjectPool (see
POOL-6). I found out now, that this bug still exists for
GenericKeyedObjectPool. Apparently, POOL-6 only solved the bug in
GenericObjectPool.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
