You should close your pool connection because the pool doesn't close the
real connection.
this doc can help you :
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-how
to.html#Random%20Connection%20Closed%20Exceptions

Arnaud

> -----Message d'origine-----
> De : Jose Euclides da Silva Junior - DATAPREVRJ
> [mailto:Jose.Euclides@(protected)]
> Envoy� : jeudi 9 octobre 2003 15:27
> � : 'tomcat-user@(protected)'
> Objet : Urgent help, please!Best practices using Connection Pool
>
>
> Hi gurus, help me please.
> i am using DBCP 1.0 to make connection pool avaiable. My
> question can be
> easy: since DBCP 1.0 doesnt create a singleton object ( just
> a datasource
> object), what should i do whenever my sql queries are done?
> Should i close
> the connection after each sql command is completed? But, if i
> do this, will
> i loose my connection pool facility, so my next sql command
> will spend more
> time since the connection process ( with the database ) would
> be started
> before the sql running. I really need to improve my database
> response time!
> Thanks in advance,
> Euclides.
>
>
> ---------------------------------------------------------------------
> 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)