In the org.ow2.petals.registry.core.repository.hibernate.HibernateHelper, we can find the following code snippet :
props.setProperty("hibernate.connection.provider_class", "org.hibernate.connection.C3P0ConnectionProvider");
props.setProperty("c3p0.acquire_increment", "1");
props.setProperty("c3p0.max_size", "2");
props.setProperty("c3p0.min_size", "1");
props.setProperty("c3p0.max_statements", "50");
props.setProperty("c3p0.idle_test_period", "100");
props.setProperty("c3p0.timeout", "300");
props.setProperty("c3p0.maxIdleTime", "300");
props.setProperty("c3p0.maxConnectionAge", "900");
props.setProperty("c3p0.automaticTestTable", "c3p0_conn_test");
props.setProperty("c3p0.idleConnectionTestPeriod", "300");
According to the C3P0 documentation, some of this properties are in conflict.
See :
http://www.mchange.com/projects/c3p0/index.html#hibernate-specific
Christophe DENEUX added a comment - Mon, 5 Oct 2015 - 11:26:34 +0200 As a new distributed registry, based on Hazelcast, has been introduced with Petals ESB 5.0.0, this issue will not be fixed.
As a new distributed registry, based on Hazelcast, has been introduced with Petals ESB 5.0.0, this issue will not be fixed.