Are you developing on the machine that you experience the problem? I found out that if I leave Tomcat running , as in production, DBCP works fine. However, if I start/stop/restart any webapp in Tomcat (such as in development) then the previous opened connections will not be closed - until i shutdown Tomcat and restart it.
Someone posted code about killing those connections when webapp is restarted. Maybe you can see if that helps.
Hope this help.
Charles
On Sunday, August 10, 2003, at 10:03 PM, Dirk Verbeeck wrote:
Hi Barclay
Maybe you should first try a different JDBC driver.
NetDirect is popular in the slide user group.
See: http://faq.globalvision.com.au/cgi-bin/fom?_recurse=1&file=45#file_94
Hope it helps Dirk
Barclay A. Dunn wrote:
hi,
i am using a try / catch / finally block to close EVERY connection in my
code. i mean 100%. however, i am still seeing connections not getting
returned to the pool.
someone on the tomcat-users list gave me code (thanks angus) to display the
connection pool state - active and idle links. i can also log in to terminal
services client and watch my sql server's connections go up (and sometimes
down, but more up than down). so what i see is, the total number that sql
server thinks are open is more than the number that the pool says are open
(active and idle). and the totals are gradually increasingly divergent.
ultimately, it crashes tomcat.
can anybody suggest how i might go about finding the holes and plugging
them? if they are not in my code, where are they?
thanks, barclay
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
