Return-Path: Delivered-To: apmail-commons-issues-archive@locus.apache.org Received: (qmail 89719 invoked from network); 16 Oct 2007 12:08:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Oct 2007 12:08:13 -0000 Received: (qmail 5465 invoked by uid 500); 16 Oct 2007 12:08:00 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 5375 invoked by uid 500); 16 Oct 2007 12:08:00 -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 5366 invoked by uid 99); 16 Oct 2007 12:08:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Oct 2007 05:08:00 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Oct 2007 12:08:11 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id D34E3714035 for ; Tue, 16 Oct 2007 05:07:50 -0700 (PDT) Message-ID: <32467447.1192536470710.JavaMail.jira@brutus> Date: Tue, 16 Oct 2007 05:07:50 -0700 (PDT) From: "Bhaskar NA (JIRA)" To: issues@commons.apache.org Subject: [jira] Created: (POOL-107) number of connections created has crossed more than maxActive MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org number of connections created has crossed more than maxActive -------------------------------------------------------------- Key: POOL-107 URL: https://issues.apache.org/jira/browse/POOL-107 Project: Commons Pool Issue Type: Bug Affects Versions: 1.3 Environment: OS:Red Hat Enterprise Linux AS release 4 (Nahant Update 2) uname:Linux 2.6.9-22.ELsmp #1 SMP Mon Sep 19 18:32:14 EDT 2005 i686 vm_info: Java HotSpot(TM) Server VM (1.4.2_13-b06) for linux-x86, built on Oct 18 2006 09:55:11 by unknown with unknown compiler Reporter: Bhaskar NA Fix For: 1.3 I found that when the minIdle is configured then during loads, common pool creates more number of connections it will be greater than maxActive. When I had following settings: maxActive = 50 maxIdle = 30 minIdle=30 factory=org.apache.commons.dbcp.BasicDataSourceFactory maxWait=10000 timeBetweenEvictionRunsMillis=900000 numTestsPerEvictionRun=50 minEvictableIdleTimeMillis=1800000 testWhileIdle=true testOnBorrow = true validationQuery='select 1 from dual' Number of connections in the pool went upto 121. (found thru netstat) When I changed minIdle to 15 and did my load test connecitons in the pool went upto 66 Looks like maxActive is getting bypassed with minIdle. When I changed minIdle to 10 and maxActive to 30 and maxIdle to 30 then number of connections went upto 40. Can someone please throw light on what is going on here? I am using DBCP 1.2.1 and common pool 1.3. Bhaskar -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.