commons-issues mailing list archives

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

                 Key: POOL-180
             Project: Commons Pool
          Issue Type: Bug
    Affects Versions: 1.5.4, 1.5.5, 1.5.3, 1.5.2, 1.5.1, 1.5
            Reporter: Phil Steitz
            Priority: Minor
             Fix For: 1.5.6

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

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