In an application I was writing I forgot closing some connections.
Despite the fact I had configured Tomcat as the example shows, no
connections was ever released.
Solutions was simple, writing better code. But I wonder if remove-abandoned
actually do what it is supposed to.
Has anyone used it with success?

P.S. MySQL Connector\j version was j3.0

Daniele


At 20.50 05/12/2003, you wrote:
>Check out "Preventing dB connection pool leaks" at:
>
>http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples
>-howto.html#Database%20Connection%20Pool%20(DBCP)%20Configurations
>
>HTH
>
>Yaakov Chaikin
>Software Engineer
>BAE SYSTEMS
>301-838-6899 (phone)
>301-838-6802 (fax)
>yaakov.y.chaikin@(protected)
>
>
> > -----Original Message-----
> > From: Michal N Lusztig [mailto:miki@(protected)]
> > Sent: Friday, December 05, 2003 11:29 AM
> > To: tomcat-user@(protected)
> > Subject: common dbcp question
> >
> >  I inherited a very badly writen Tomcat4.1 application, where the
> > developer is not
> > closing connections, relying rather on configuration parameters for
>the
> > dbcp pool to take care of removing abandoned connections. Is such a
> > strategy supposed to work ? If yes, what are the configuration
> > parameters that would solve this problem ? Reading the
> > documentation in DBCP dataSource, it looks like remove_abandoned is
> > depracated !
> >
> >
> > Miki
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
> > For additional commands, e-mail: tomcat-user-help@(protected)
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
>For additional commands, e-mail: tomcat-user-help@(protected)


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)