I'm running a servlet on Tomcat 4.1.24 for Hibernate 2.0.3. I use C3P0 in my hibernate.cfg.xml files. When I try to close the factory using my SessionFactory's close() call, the C3P0 pool is being orphaned, not shut down. This is eating up my memory and leaving database connections open. Does anyone have any suggestions?

My hibernate.cfg.xml file is this:

<hibernate-configuration>
<!-- a SessionFactory instance listed as /jndi/name -->
<session-factory>
<!-- properties -->
<!-- property name="connection.datasource">my/first/datasource</property> -->
<property name="dialect">net.sf.hibernate.dialect.MySQLDialect</property>
<property name="connection.username">someDBUser</property>
<property name="connection.password">someDBPAss</property>
<property name="connection.url">jdbc:mysql://localhost:3306/someDB?autoReconnect=true</property>
<property name="connection.driver_class">com.mysql.jdbc.Driver</property>
<property name="show_sql">false</property>
<property name="use_outer_join">true</property>
<property name="transaction.factory_class">net.sf.hibernate.transaction.JDBCTransactionFactory</property>
<property name="c3p0.max_size">20</property>
<property name="c3p0.min_size">2</property>
<property name="c3p0.timeout">3600</property>
<property name="c3p0.max_statements">100</property>
<property name="c3p0.valudate">false</property>

<!-- mapping files -->
<mapping resource="Misc.hbm.xml"/>
</session-factory>
</hibernate-configuration>

Thanks for any suggestions.

Regards,
David

I must've mis-clicked as I thought I was posting to the beginners forum since a form 'search' turned up nothing useful.

Regards,
David

use dbcp instead of c3p0.

Or even better, if you are running in a container like JBoss use datasources managed by the container.

I'd emailed Steve Waldman about his C3P0 project and got this response about the 0.8.3 C3P0 passed out with Hibernate 2.0.2 & 2.0.3:

---------------
You'll have to upgrade to the latest 0.8.4 test release, but if you do,
you can force DataSources to clean themselves up by calling the static
method DataSources.destroy(DataSource pooledDataSource ), or
equivalently by casting the DataSource to a
com.mchange.v2.c3p0.PooledDataSource and calling its close() method.
---------------

Regardless, yesterday I commented out my C3P0 settings and added
<property name="dbcp.minIdle">1</property>
to my hibernate.cfg.xml files. It got rid of most of my emory problems since C3P0 was eating up memory. I think I still have a leak somewhere but I haven't found it yet (though I'm sure I've freed everything up).

Regards,
David

cool, I'll support this new feature when 0.8.4 final is released.