nl_age,
Sorry about the delayed response. The pool is not being closed at all -- only a single PooledConnection. This might happen if c3p0 has detected that a Connection has gone stale, or if a Connection has exceeded its maximum idle time in the pool.
Please feel free to write me with any c3p0 issues at
swaldman@mchange.com (or use
c3p0-users@lists.sourceforge.net). I monitor the hibernate forums only very intermittently, but I do try to respond to c3p0-related email quckly!)
Steve
p.s. there is no way to turn off the debug message -- c3p0's logging strategy is rudimentary: I need to comment out the System.err.println(...) statement! (I know... I know... in this day and age...) It'll be gone in the next minor release of c3p0.