ERROR JDBCExceptionReporter - com.mchange.v2.c3p0.PoolBackedDataSource@64b75e80

[Lorenzo5]

Hi, 

the technical.log (the log configured in TAC-->Settings-->Configuration-->Log4j-->"Technical file appender") logs the following error every second:

------

2017-09-21 15:34:02 ERROR SocketAppenderWithEmergencyLocalAppender - com.mchange.v2.c3p0.PoolBackedDataSource@64b75e80 [ connectionPoolDataSource -> com.mchange.v2.c3p0.WrapperConnectionPoolDataSource@30678b73 [ acquireIncrement -> 1, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoCommitOnClose -> false, automaticTestTable -> null, breakAfterAcquireFailure -> false, checkoutTimeout -> 0, connectionCustomizerClassName -> null, connectionTesterClassName -> com.mchange.v2.c3p0.impl.DefaultConnectionTester, debugUnreturnedConnectionStackTraces -> false, factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false, identityToken -> 2sitqm9q18b1t7l1lsm94d|69682fa9, idleConnectionTestPeriod -> 250, initialPoolSize -> 1, maxAdministrativeTaskTime -> 0, maxConnectionAge -> 0, maxIdleTime -> 300, maxIdleTimeExcessConnections -> 0, maxPoolSize -> 32, maxStatements -> 0, maxStatementsPerConnection -> 0, minPoolSize -> 1, nestedDataSource -> com.mchange.v2.c3p0.DriverManagerDataSource@ebbb719d [ description -> null, driverClass -> null, factoryClassLocation -> null, identityToken -> 2sitqm9q18b1t7l1lsm94d|43f5c1f1, jdbcUrl -> jdbcostgresql://bitldmgr_app01-db:5432/bitldmgr_app01_migration, properties -> {user=******, password=******} ], preferredTestQuery -> null, propertyCycle -> 0, testConnectionOnCheckin -> false, testConnectionOnCheckout -> false, unreturnedConnectionTimeout -> 0, usesTraditionalReflectiveProxies -> false; userOverrides: {} ], dataSourceName -> null, factoryClassLocation -> null, identityToken -> 2sitqm9q18b1t7l1lsm94d|6befa8cc, numHelperThreads -> 3 ] has been closed() -- you can no longer use it.

2017-09-21 15:34:02 ERROR JDBCExceptionReporter - com.mchange.v2.c3p0.PoolBackedDataSource@64b75e80 [ connectionPoolDataSource -> com.mchange.v2.c3p0.WrapperConnectionPoolDataSource@30678b73 [ acquireIncrement -> 1, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoCommitOnClose -> false, automaticTestTable -> null, breakAfterAcquireFailure -> false, checkoutTimeout -> 0, connectionCustomizerClassName -> null, connectionTesterClassName -> com.mchange.v2.c3p0.impl.DefaultConnectionTester, debugUnreturnedConnectionStackTraces -> false, factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false, identityToken -> 2sitqm9q18b1t7l1lsm94d|69682fa9, idleConnectionTestPeriod -> 250, initialPoolSize -> 1, maxAdministrativeTaskTime -> 0, maxConnectionAge -> 0, maxIdleTime -> 300, maxIdleTimeExcessConnections -> 0, maxPoolSize -> 32, maxStatements -> 0, maxStatementsPerConnection -> 0, minPoolSize -> 1, nestedDataSource -> com.mchange.v2.c3p0.DriverManagerDataSource@ebbb719d [ description -> null, driverClass -> null, factoryClassLocation -> null, identityToken -> 2sitqm9q18b1t7l1lsm94d|43f5c1f1, jdbcUrl -> jdbcostgresql://bitldmgr_app01-db:5432/bitldmgr_app01_migration, properties -> {user=******, password=******} ], preferredTestQuery -> null, propertyCycle -> 0, testConnectionOnCheckin -> false, testConnectionOnCheckout -> false, unreturnedConnectionTimeout -> 0, usesTraditionalReflectiveProxies -> false; userOverrides: {} ], dataSourceName -> null, factoryClassLocation -> null, identityToken -> 2sitqm9q18b1t7l1lsm94d|6befa8cc, numHelperThreads -> 3 ] has been closed() -- you can no longer use it.

2017-09-21 15:34:02 WARN SocketAppenderWithEmergencyLocalAppender - !!!Cannot create session or transaction.!!!

2017-09-21 15:34:02 WARN RemoteTaskExecution - !!!Cannot create session or transaction.!!!
------

Any idea what has been causing it?

If not, I will open a case to the support team.

Regards,

Lorenzo

[Anonymous · Accepted solution]

Hello,

When did this problem occurs?  From the error message, it seems that your Database connection is not released correctly. More information will be needed to address your issue.

It's strongly recommended that you should create a case on talend support portal. In this way, we can schedule a webex and give you a remoted assistance.

Best regards

Sabrina

[Lorenzo5]

Thanks, 

we found the reason, it is a DB fail, indeed.

Regards,

Lorenzo

[Anonymous]

Hello,

Thanks for letting us know the reason.

Best regards

Sabrina

[jscher01]

Hello Lorenzo,

I am seeing this error in my TAC log but the database seems fine. Do you mind sharing what was causing the DB issue?

Thanks,

James