[
https://issues.apache.org/jira/browse/POOL-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Thomas resolved POOL-180.
------------------------------
Resolution: Fixed
Assignee: Mark Thomas
Fixed in 1.5.x and trunk. There was actually a bigger issue in that the
tracking information was being thrown away too soon. Fixing that and the issue
Phil noticed, allowed the test case to complete.
> 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
> Assignee: Mark Thomas
> 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
