tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Turner <>
Subject Re: Connection Pool Woes
Date Fri, 20 Jan 2006 19:15:41 GMT
How do you deal with this when using pure JSTL sql calls using a
connection?  How does JSTL sql library release the connection at the
end of a page to ensure that connections don't get leaked?  For the
case when I'm using a servlet, I have put in an explicit close() call
on the connection, but some pages are pure JSP.


On 1/20/06, Caldarale, Charles R <> wrote:
> > -----Original Message-----
> > From: Alex Turner []
> > Subject: Re: Connection Pool Woes
> >
> > It looks like the connection object was not being garbage collected
> > promptly (imagine that), and because it wasn't explicitly closed, it
> > was just hanging open until garbage collection happened (I'm more used
> > to python's garbage collector that is a bit more prompt).
> Garbage collection should have nothing to do with it; don't confuse
> finalizers with finally clauses.  If your application operation is
> dependent on a finalizer, you're in a world of hurt.  There is no
> guarantee that a finalizer will _ever_ be run.
>  - Chuck
> MATERIAL and is thus for use only by the intended recipient. If you
> received this in error, please contact the sender and delete the e-mail
> and its attachments from all computers.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message