hi list! this is my first post to this list :) i have searched this list's archives but could not find a lot about that topic so i am posting it. i am not sure if this is really a tomcat issue; if it is not i hope someone may point me the right direction.
i develop JSP applications (tomcat4, java 1.4, postgres database7.4 with jdbc connectivity, the OS is linux 2.6.8, debian sarge) with CodeCharge Studio (yessoftware.com) which create a connection pool of, say 10 connections. when i upload a new version of an application to the server tomcat reloads the context correctly but it seems that open database connections continue to exist forever and are never closed. on initialisation the newly uploaded app creates new database connections so after so-many uploads i of course run into a max_connections_exceeded error from the database. the connections are closed only when i restart tomcat. who should take care of open db connections? my guess is that tomcat should do so when it reloads the context. is that assumption wrong? is there a way to make tomcat close idle db connections after some timeout? -- best rgds, armin walland focus media research IT :: development, administration focusmr.com maculangasse 8 1220 wien +43 (0)1-258 97 01 291 please try not to send me HTML emails! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
