Sorry for not replying directly to the thread. My web-email ( via netscape ) has barfed and I had to re-subscribe under a different email. Anyway, to clarify: When the servlet engine restarts due to a jar update, the connection pool is never destroyed. I placed a line to write to the log in the finalize() method and it looks like it is never being destroyed. Then, when Turbine restarts, a new DBBroker ( and connection pool ) is created, leaving the other one hanging. I did verify that I have the turbine jar in the context for the web app ( or jserv's zone ) and not in the system classpath. I've verified this under tomcat and jserv. Both had the jars in the correct place ( ie: not is the system path ). ----------------------------------------------------------------------- This message has been scanned for viruses with Trend Micro's Interscan VirusWall. ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/> Problems?: [EMAIL PROTECTED]
