From: Gavin_King/Cirrus%<CI...@ci...> - 2002-05-18 04:06:07
|
Ages ago, Brad Clow wrote: > PoolMan (http://www.codestudio.com) is no longer supported by its > developer and we found that the last release had some issues. it may > yet end up with the jakarta project > (http://jakarta.apache.org/site/elsewhere.html#0305). I tried out various versions of PoolMan with hibernate and concluded that Brad is correct. It has issues and since no longer supported, I imagine they won't be going away! (The issues were bad enough that I couldn't run test suite.) On the other hand, c3p0 bugs get fixed immediately I find them. I would _love_ to get some feedback about how peoples applications perform with c3p0 pooling enabled, compared to hibernate's own (crap) connection pool. You need to set the following properties hibernate.c3p0.max_size {max size of connection cache} hibernate.c3p0.min_size {min size of connection cache} hibernate.c3p0.timeout {max time a connection can remain idle} hibernate.c3p0.max_statements {size of statement cache} hibernate.pool_size 0 You may want to grab the latest jar from http://sourceforge.net/projects/c3p0 Or from lib directory in our CVS. |