Hello,

We are currently using Hibernate in a commerical product.
I would like to know how can we disable the log level for c3po, since during the initialization it shows all the configuration including the user name and password to connect the database into the logger

Initializing c3p0 pool... com.mchange.v2.c3p0.PoolBackedDataSource@164b9b6 [ connectionPoolDataSource -> com.mchange.v2.c3p0.WrapperConnectionPoolDataSource@8acfc3 [ acquireIncrement -> 2, autoCommitOnClose -> false, connectionTesterClassName -> com.mchange.v2.c3p0.impl.DefaultConnectionTester, factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false, idleConnectionTestPeriod -> 3000, initialPoolSize -> 5, maxIdleTime -> 1800, maxPoolSize -> 20, maxStatements -> 50, minPoolSize -> 5, nestedDataSource -> com.mchange.v2.c3p0.DriverManagerDataSource@1dc64a5 [ description -> null, driverClass -> null, factoryClassLocation -> null, jdbcUrl -> jdbc:mysql:///fts, properties -> {user=root, password=root} ] , propertyCycle -> 300, testConnectionOnCheckout -> false ] , factoryClassLocation -> null, numHelperThreads -> 3 ]
2005-12-21 19:25:53,434 WARN (Configurator.java:125) No configuration found. Configuring ehcache from ehcache-failsafe.xml found in the classpath: file:/jakarta-tomcat-5.0.30/work/Catalina/localhost/fts/loader/ehcache-failsafe.xml

We use log4j

Thanks in advance

H 3.1 CVS does not give away password, but shows db user:
log.info( "Connection properties: " + PropertiesHelper.maskOut(connectionProps, "password") );

To prevent printing from C3P0ConnectionProvider add the following line to your log4j.properties file:
log4j.logger.org.hibernate.connection.C3P0ConnectionProvider=fatal

kgignatyev,

I'm using c3p0 version 0.8.4.5 and Hibernate 2.18.
Putting the log level for the package you gave me does not work. Probably becasue I'm using another H version.

Albert

For H2 I believe it will be
log4j.logger.net.sf.hibernate.connection.C3P0ConnectionProvider=fatal

Sorry, but this also does not work.

Albert