[POOL-3] [pool] GenericObjectPool WHEN_EXHAUSTED_BLOCK behvior could wait almost twice as long as desired

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

Environment

Operating System: All
Platform: All

• Bugzilla Id: 37337
• Assignee: Unassigned
• Reporter: Sandy McArthur (from Bugzilla import)
• Created: 03/Nov/05 06:49
• Updated: 12/Sep/10 17:42
• Resolved: 12/Sep/10 17:42

Description

Very minor bug: On lines 797 of GenericObjectPool and lines 809 of GenericKeyedObjectPool the code is
such that if the pool is exhausted and the thread waits and is notified shortly before _maxWait time has
elapsed then then the thread may end up waiting for another period of _maxWait. Combined with the
previous wait the thread could have actually waited almost twice the desired time. The correct behavior
would be to do the math and wait a lesser amount adjusted for the previous wait interval.