Hi

I'm using tomcat 4.0.x, Hibernate 1.2.5 and Postgresql 7.3.

Using Apache DBCP for connection pooling.

The propblem i'm having is this:
The tomcat Context is set reloadable="true" and i don't have access to any of the tomcat configurations. Normally this wouldn't be a problem but when tomcat reloads the context it leaves the old versions connections to the db open and idle. This results in postgresql refusing to issue new db connections after reaching its limit.

I create / load SessionFactory in a Servlet loaded on Context Initialisation.

Is there a way to close those old connections or am i doing somethign to cause this ?

Keep in mind i cannot alter the configs for apache or tomcat myself - only the configs for the web app.

thanks

pd

Do you then also close the session factory on the context destroyed event?

Thanks.

I was using Servlet loaded on startup to do this, You suggestion lead me to the ServletContextListener which seems to be a neater way of doing something that was somewhat messy to start with.

Thanks muchly

Are there any other possibilities to look into? I'm closing the SessionFactory when the context is destroyed but dead db connections are being left to accumulate. I'm using Postgres 7.3 with Tomcat 4 and 5 (both give the problem) and the JNDI database access method with org.postgresql.jdbc2.optional.PoolingDataSource and org.postgresql.jdbc2.optional.PGObjectFactory.

thanks.