Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <11186568.1194199370600.JavaMail.jira@brutus>
Date: Sun, 4 Nov 2007 10:02:50 -0800 (PST)
From: "Phil Steitz (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Commented: (POOL-107) number of connections created has
 crossed more than maxActive
In-Reply-To: <32467447.1192536470710.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/POOL-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540086 ] 

Phil Steitz commented on POOL-107:
----------------------------------

The pool code to ensure minIdle should not cause this to happen.  
Can you provide some more information on your setup and load test?  In particular,
How is the DBCP datasource being instantiated?  Is DBCP running in a web container?
What is the database? Is it remote from the host running the pool?  Are all of the TCP connections ESTABLISHED?  Are you sure they are all associated with the client connection pool?  
Are client threads timing out waiting for connections during the test (i.e.., do you see org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object)?
What does the DBCP client do with connections obtained during the test?
Is the load constant, with threads just repeating the same requests with no delays in between requests?
What is the duration of the test?


> 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.