Return-Path: Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: (qmail 21532 invoked from network); 5 Jan 2011 02:17:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Jan 2011 02:17:07 -0000 Received: (qmail 52330 invoked by uid 500); 5 Jan 2011 02:17:07 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 52191 invoked by uid 500); 5 Jan 2011 02:17:07 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 52169 invoked by uid 99); 5 Jan 2011 02:17:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Jan 2011 02:17:06 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Jan 2011 02:17:06 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id p052Gk5V016692 for ; Wed, 5 Jan 2011 02:16:46 GMT Message-ID: <30481292.150911294193806145.JavaMail.jira@thor> Date: Tue, 4 Jan 2011 21:16:46 -0500 (EST) From: "Phil Steitz (JIRA)" To: issues@commons.apache.org Subject: [jira] Created: (POOL-180) Max active per key can be exceeded by one MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 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.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 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.