Hello,

I am using hibernate 3.6.1 with hibernate-c3p0-3.6.1.Final.jar and c3p0-0.9.1.

The managed c3p0 connections gradually increases until it reaches it's max limit. This can be seen in the c3p0 logs, e.g.

trace com.mchange.v2.resourcepool.BasicResourcePool@26193229 [managed: 72, unused: 2, excluded: 0] (e.g. com.mchange.v2.c
3p0.impl.NewPooledConnection@3088890d)

These are the c3p0 properties:
hibernate.c3p0.min_size=5
hibernate.c3p0.max_size=80

The application is not in a production environment and does not require that many connections. It can run with as little as 10 connections and therefore I am suspecting a connection leak. I have added these two properties in c3p0 in an attempt to identify the cause of the leaks:

c3p0.debugUnreturnedConnectionStackTraces=true
c3p0.unreturnedConnectionTimeout=600

However the c3p0 logs show that these properties are ignored:

com.mchange.v2.resourcepool.BasicResourcePool@26193229 config: [start -> 5; min -> 5; max -> 80; inc -> 3; num_acq_attempts -> 30; acq_attempt_delay -> 1000; check_idle_resources_delay -> 180000; mox_resource_age -> 0; max_idle_time -> 1800000; excess_max_idle_time -> 0; destroy_unreturned_resc_time -> 0; expiration_enforcement_delay -> 450000; break_on_acquisition_failure -> false; debug_store_checkout_exceptions -> false]

I am expecting to see:

debugUnreturnedConnectionStackTraces -> true

As a parameter in the c3p0 logs.

The application does not output stack traces on connection checkout or refurbishing.

Does this have to do with the fact that the BasicResourcePool is instantiated? Why are these parameters ignored?

Your input would be much appreciated

Put a breakpoint in the constructor of BasicResourcePool to determine why that field isn't being set properly.