Maxwait exceeded causes pool capacity leak
------------------------------------------
Key: POOL-144
URL: https://issues.apache.org/jira/browse/POOL-144
Project: Commons Pool
Issue Type: Bug
Affects Versions: 1.5
Reporter: Phil Steitz
Attachments: latch_leak.patch
When exhausted action is set to WHEN_EXHAUSTED_BLOCK, maxwait is positive and
client threads time out waiting for idle objects, capacity can be "leaked" from
GenericObjectPools and GeneritCkeyedObjectPools.
Test case and patch for GOP attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
