Expand the bit to Corey's answer:
If unverturnedConnectionTimeout is positive, and debugUnreturnedConnectionStackTraces is true, then stack traces that throw unexecuted Exceptions will be logged at the INFO level by the "com.mchange.v2.resourcepool.BasicResourcePool" logger.
Often people log something above the INFO level from all loggers, so these stack traces are only shown in your logs. But if you do not see them, check the logging configuration to make sure that messages in the INFO from this logger are not filtered out.
Note that debugUnreturnedConnectionStackTraces will do nothing if the non-return ConnectionTimeout is also not set.
Cm
http://www.mchange.com/projects/c3p0/#unreturnedConnectionTimeout
http://www.mchange.com/projects/c3p0/#debugUnreturnedConnectionStackTraces
Hope this helps!
ps it doesn't matter how you set these properties if they are set correctly. c3p0 pool configurations in INFO when starting the pool; check your logs to make sure that while you are trying to set the parameters, you have the configuration that you expect. Alternatively, you can use JMX to check the parameters.
source share