[ https://issues.apache.org/jira/browse/POOL-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742303#action_12742303 ]
Krystian Szczesny commented on POOL-107: ---------------------------------------- Hi We were using commons-pool 1.4 in our application and we came across this issue. Unfortunately it is critical for us :/ When I have a setting of: max active: 10 max:idle 5 min idle:2 When running test with 20 threads I get: before test is ran: num active: 0 num idle: 2 during test: num active: 20 num idle: 0 after the test is done: num active: 0 num idle: 5 I've updated commons-pool to 1.5.2 and unfortunately same thing happens, I cannot control maximum of active connections! I've tried changing the min idle and max idle to many different settings but was never able to limit the number of active connections! > 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. - You can reply to this email to add a comment to the issue online.