[POOL-6] [pool] Number of tested objects in eviction runs of GenericObjectPool

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.2
• Fix Version/s: 1.3

Environment

Operating System: All
Platform: All

• Bugzilla Id: 33265
• Assignee: Unassigned
• Reporter: Thomas Schürger
• Created: 27/Jan/05 17:05
• Updated: 12/Sep/10 17:42
• Resolved: 12/Sep/10 17:42

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.

Issue Links

• relates to: POOL-145 Number of tested objects in eviction runs of GenericKeyedObjectPool