Hello Hibernate "c3p0 guy" - you may be the only one who can help
resolve this issue:

This message appears persistenly:

02:49:21,102 DEBUG NewPooledConnection:566 - com.mchange.v2.c3p0.impl.NewPooledConnection@9c5167 closed by a client.
java.lang.Exception: DEBUG -- CLOSE BY CLIENT STACK TRACE
at com.mchange.v2.c3p0.impl.NewPooledConnection.close(NewPooledConnection.java:566)
at com.mchange.v2.c3p0.impl.NewPooledConnection.close(NewPooledConnection.java:234)
at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.destroyResource(C3P0PooledConnectionPool.java:470)
at com.mchange.v2.resourcepool.BasicResourcePool$1DestroyResourceTask.run(BasicResourcePool.java:964)
at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)

I am using Hibenate 3.2 and c3p0-0.9.1.2.

THE QUESTION: Is this significant or can this be ignored ?
(i.e.: is connection pooling working properly ?)

Note:
Am using a basic c3p0 config in hibernate.cfg.xml:
<property name="c3p0.acquire_increment">1</property>
<property name="c3p0.min_size">5</property>
<property name="c3p0.max_size">20</property>
<property name="c3p0.timeout">300</property>
<property name="c3p0.max_statements">50</property>
<property name="c3p0.idle_test_period">3000</property>

<property name="transaction.factory_class">org.hibernate.transaction.JDBCTransactionFactory</property>

If indeed it is the case that these messages are debug only
but do not indicate that pooling is not working, then the
issue becomes one of:

How to turn them off (evidently:
"Logging-related parameters may be placed in your c3p0.properties file,
in a file called mchange-log.properties" and
"com.mchange.v2.log.FallbackMLog.DEFAULT_CUTOFF_LEVEL" may
be set to suppress these debug messages, according to the c3p0
documentation)

or:

How can I recompile c3p0 source (I tried under jdk1.6 but got
errors) so that this particular message is suppressed, as I did
find this message in the c3p0 source code.

Right now I am using apache dbcp for the pooling, because the
c3p0 DEBUG messages cast doubt on the integrity of c3p0's
pooling.

Am much obliged if you can help,

Maurice Yarrow