Hi.
c3p0 does not dump the connection pool size to the console or log, unless you edit the source to put it in debug mode with maximum tracing. The pool size may change frequently. To check the pool size, cast your DataSource to the PooledDataSource interface and call the appropriate method. (See the docs and javadocs.)
c3p0 does indeed pay attention to the parameters you supply, but does not check and warn you if you supply foolish or inconsistent parameters. If you provide a minimum size of 70 and a maximum size of 0, c3p0 will (dutifully) acquire 70 initial connections, but will never acquire another Connection, even if some die and the count goes below 70, because the size will always be above the maximum size.
I can add some sanity checks, but it's not been a priority. If you use sane values and documented special values, c3p0 will honor them. If you use unreasonable values, c3p0's behavior is, um, "undefined".
smiles,
Steve
|