Joined: Mon Sep 15, 2003 2:20 am Posts: 4
|
Hi
Can anyone explain what is the matchup with the hibernate.properties for the C3P0 connection pooling versus the C3P0 API documentaition.
I want to use the ' idleConnectionTestPeriod' to ensure that connections aren't destroy across a firewall. What i've discovered is that these settings appear to be ignored when specified in the hibernate.properties file. I tried placing a c3p0.properties in the WEB-INF/classes directory so that the class loader can locate it. What i found is that if i don't have any references to c3p0 in hibernate.properties i can't see the c3p0 connection pool initialised.
Looking at the Hibernate docs i can see the options :
hibernate.c3p0.max_size
hibernate.c3p0.min_size
hibernate.c3p0.timeout
hibernate.c3p0.max_statements
hibernate.c3p0.validate_connection
For C3P0 there is:
c3p0.initialPoolSize
c3p0.minPoolSize
c3p0.maxPoolSize
c3p0.idleConnectionTestPeriod
c3p0.maxIdleTime
c3p0.maxStatements
c3p0.propertyCycle
c3p0.acquireIncrement
c3p0.testConnectionOnCheckout
c3p0.autoCommitOnClose
c3p0.forceIgnoreUnresolvedTransactions
c3p0.connectionTesterClassName
c3p0.numHelperThreads
c3p0.factoryClassLocation
Any suggestions are most welcome since i've been struggling with a firewall, jdbc connection + tomcat problem for 2 weeks and have done all the rounds with DBCP - c3p0 is my last option !
grant
|
|