[
https://issues.apache.org/jira/browse/POOL-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010214#comment-13010214
]
Phil Steitz commented on POOL-180:
----------------------------------
I have also been working on a fix for this. It gets a little messy because
clear() and clearOldest() both need to have their accounting fixed and you need
to postpone removing depleted pools from _poolMap until after destroy completes
so you can continue to track internal processing count for the depleted pool.
One other thing I noticed is that clear does not seem to clear _poolMap.
Sorry the test case was messed up.
> Max active per key can be exceeded by one
> -----------------------------------------
>
> Key: POOL-180
> URL: https://issues.apache.org/jira/browse/POOL-180
> Project: Commons Pool
> Issue Type: Bug
> Affects Versions: 1.5, 1.5.1, 1.5.2, 1.5.3, 1.5.5, 1.5.4
> Reporter: Phil Steitz
> Priority: Minor
> Fix For: 1.5.6
>
> Attachments: maxAcitivePerKeyExceededTest.patch
>
>
> When instances in the pool fail validation with high frequency, maxTotal is
> less than maxActive times the number of keys, and destroy has latency, the
> maxActive contract can be violated (i.e., the number of instances created
> under a given key minus the number destroyed can exceed maxActive).
> Attaching a test case that fails against POOL_1_X
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
