commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <>
Subject [jira] Commented: (POOL-180) Max active per key can be exceeded by one
Date Wed, 05 Jan 2011 04:34:45 GMT


Phil Steitz commented on POOL-180:

I think the problem is in clearOldest/destroy where only _totalInternalProcessing is incremented/decremented.
 The individual key processing counts need to be updated as well.  When clearOldest is disabled,
the test succeeds.

> Max active per key can be exceeded by one
> -----------------------------------------
>                 Key: POOL-180
>                 URL:
>             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.
You can reply to this email to add a comment to the issue online.

View raw message