tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "neal" <nealcab...@yahoo.com>
Subject RE: DBCP Woes!
Date Tue, 29 Oct 2002 00:58:53 GMT
I was releasing them in the Try, not the finally - just after requesting a
connection and using a connection.

I see your point that this isn't ideal and I should change definitely change
this.  Still though, unless enough errors occured (after the conneciton
requerst and before the conneciton release) to deplete my pool (in this case
100), this shouldn't have exhausted my pool shoult it have?

Thanks.
Neal


-----Original Message-----
From: Dan Lipofsky [mailto:danlip@nuserve.com]
Sent: Monday, October 28, 2002 3:55 PM
To: nealcabage@yahoo.com
Subject: Re: DBCP Woes!


Are you releasing connections in the "finally"
block of a try/catch/finally statement?
- Dan

> DBCP works fine initially but seems the conn pool is exhausted quickly, as
> if the connections aren't being released.  But I made sure last night that
> every Sonnection and Statement object is closed and nullified so I am
> suprised Im still having this error.
>
> On thing of interested.  Prior to receiving the connection pool exhausted
> error, I recieve this error:
>
> javax.naming.NameNotFoundException: Name jdbc is not bound in this Context
>
> Might this mean there is something else, other than simple release of
> Connections happening here?  Any ideas what this might mean?


--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@jakarta.apache.org>


Mime
View raw message