Can you determine with certainty that this one pool was responsible for
all 121 connections? You don't have any other webapps with their own
pool hitting the same db?
--David
Bhaskar wrote:
Hi,
I am currently using dbcp 1.2.1 with common pool 1.3. Currently i have
following settings in server.xml:
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'
Issue is when i restarted tomcat, i seen there were only 6 connections.
After 15 minutes, i see there were 121 connections in netstat against oracle
port.
Can someone please help me understand the DBCP behaviour here? how can it go
beyond maxActive?
Thanks,
Bhaskar
System info:
--------------- S Y S T E M ---------------
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
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
