I am using hibernate in a JSP application deployed in Tomcat.

In Postgres I see that I tend to acumulate a lot of idle connections when developing my application. I figured out that I am creating 2 connections in my C3p0 managed connection pool on each deplyoment, which remain idle (and inaccessible) after I redeploy the application.

Because I'm using a static variable for my sessionfactory, I believe the reason for these idle connections that acumulate is the fact that I'm not closing the SessionFactory before I undeploy the application.

How can I close everything up before I redeploy the application. I use Ant to deploy/undeploy/redeploy the application in Eclipse.

You clean up the SessionFactory by calling SessionFactory.close(). If your question is how you do know when to call it, that is, how does Tomcat let your application know it is being undeployed, that's a question for the Tomcat folks.

=Jeremy=

Yes, my question was regarding when to call the close() method.

For those interested, one solution is to implement a ServletContextListener and put the sessionfactory.close() on its contextdestroyed method.