commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Victor N (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (POOL-107) number of connections created has crossed more than maxActive
Date Wed, 28 Dec 2011 07:54:32 GMT

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

Victor N commented on POOL-107:
-------------------------------

The problem with minIdle still exists in 1.5.7, steps to reproduce:

1) start connection pool with **disconnected** database (I used mysql and stopped it)
2) try to execute several qieries - yes, you will get errors of course
3) turn on the database
4) execute some queries (their quantity should be > maxActive)
5) look at connection count from database side, it will be > maxActive and will increase
at each query (until limit in database is reached)

So, the problem still occurs when you start working with database turned off and then you
turn it on. But I can confirm that if you start with database already turned on, then no problem!

My config was:

		<property name="initialSize" value="10" />
		<property name="minIdle" value="5" />

		<property name="maxActive" value="30" /><!-- -1="no limit" -->

		<property name="maxWait" value="10000" />				

		<property name="timeBetweenEvictionRunsMillis" value="60000" />

		<property name="minEvictableIdleTimeMillis" value="300000" />

		<property name="testOnBorrow" value="false" />

		<property name="testOnReturn" value="false" />

		<property name="testWhileIdle" value="true" />

		<property name="validationQuery" value="SELECT 1 FROM DUAL" />

                
> 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.5
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message