Also, if you have a connection leak, then DBCP will continue to create
connections to meet demand, even if the old connections are not closed.
Since they are no longer in the "pool" (since they were never returned),
they don't count against the "size" of the pool.
Huh?? Borrowed objects are still in the pool, just marked as borrowed
so they don't go out to another request. If the pool fills to capacity
with all items borrowed future requests either wait or are denied until
borrowed connections are returned. I suspect there is more than one
pool at work here.
--David
Christopher Schultz wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bhaskar,
Bhaskar wrote:
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?
Are you sure all those connections are from the DBCP?
Also, if you have a connection leak, then DBCP will continue to create
connections to meet demand, even if the old connections are not closed.
Since they are no longer in the "pool" (since they were never returned),
they don't count against the "size" of the pool.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHE2/Q9CaO5/Lv0PARAsvzAKCDTtMaBTBDhdWxZtloYze8RVJZwgCfajE6
XHS+EVHNks6d8N7pFlNgdr4=
=7wZP
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
