Re: More number of connections got created than maxActive

2007-10-17 Thread David Smith
Users List Subject: Re: More number of connections got created than maxActive Isn't it http://issues.apache.org/jira/browse/DBCP-28 ? "Connection leak ..." It was fixed in DBCP 1.2.2. You may want to read through the Release History of DBCP for other bugs that have been already fo

RE: More number of connections got created than maxActive

2007-10-17 Thread Bhaskar
l 1.3)? Bhaskar > -Original Message- > From: Konstantin Kolinko [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 16, 2007 8:57 PM > To: Tomcat Users List > Subject: Re: More number of connections got created than maxActive > > Isn't it http://issues

Re: More number of connections got created than maxActive

2007-10-16 Thread Konstantin Kolinko
Isn't it http://issues.apache.org/jira/browse/DBCP-28 ? "Connection leak ..." It was fixed in DBCP 1.2.2. You may want to read through the Release History of DBCP for other bugs that have been already found and fixed, http://commons.apache.org/dbcp/changes-report.html -

RE: More number of connections got created than maxActive

2007-10-16 Thread Bhaskar
[mailto:[EMAIL PROTECTED] > > Sent: Monday, October 15, 2007 6:59 PM > > To: Tomcat Users List > > Subject: Re: More number of connections got created than maxActive > > > > Can you determine with certainty that this one pool was responsible > > for a

RE: More number of connections got created than maxActive

2007-10-15 Thread Bhaskar
More number of connections got created than maxActive > > 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: > > &

Re: More number of connections got created than maxActive

2007-10-15 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David, David Smith wrote: >> 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),

Re: More number of connections got created than maxActive

2007-10-15 Thread David Smith
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 ar

Re: More number of connections got created than maxActive

2007-10-15 Thread Christopher Schultz
-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 her

Re: More number of connections got created than maxActive

2007-10-15 Thread David Smith
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 serv