[
https://issues.apache.org/jira/browse/POOL-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719162#action_12719162
]
Mark Thomas commented on POOL-144:
----------------------------------
I agree with your analysis. I'd also add that similar problems can occur in
each of the case statements. When a thread enters a sync block, there needs to
be a check that another thread hasn't allocated an object whilst the current
thread was waiting for a lock.
I have a patch for GOP and GKOP. I'll commit it shortly.
> 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
> Fix For: 1.5.1
>
> 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.
