When application running under extreme loads we observed a deadlock in two application threads where in one is trying to check-in after use and other is trying to open a connection. The java stack was taken using the kill -QUIT command on Solaris environment shows a deadlock between BasicResourcePool and ThreadPoolAsynchronousRunner objects. Tried looking at the code and also stack does not show where the lock to the runner object is held.
We are using C3P0 version 0.9.1.2. and below are the c3p0 properties through hibernate
Properies in c3p0