[POOL-145] Number of tested objects in eviction runs of GenericKeyedObjectPool

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.5.1
• Fix Version/s: 1.5.2

Environment

Operating System: All
Platform: All

• Assignee: Unassigned
• Reporter: Klaus Kopruch
• Created: 18/Jun/09 13:09
• Updated: 14/Jul/09 01:13
• Resolved: 19/Jun/09 15:59

Description

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.

[e-mail] 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.

Issue Links

• is related to: POOL-6 [pool] Number of tested objects in eviction runs of GenericObjectPool