Nayar, I've configured c3p0 to do all that and the logs at the beginning seems to confirm that, but since the broken connection is still holded, it cannot do anything. Hence this message, I guess: com.mchange.v2.c3p0.impl.NewPooledConnection.handleThrowable [c3p0] A PooledConnection that has already signalled a Connection error is still in use!
I've configured idleConnectionTestPeriod and preferredTestQuery defaults to the listing of the tables. Thanks. On Mon, Jan 4, 2016 at 8:20 PM, SaurabhNayar <nayar.saur...@gmail.com> wrote: > Please refer to: > > > http://www.mchange.com/projects/c3p0/index.html#configuring_connection_testing > < > http://www.mchange.com/projects/c3p0/index.html#configuring_connection_testing > > > > You can use: > /idleConnectionTestPeriod > preferredTestQuery/ > > parameters to make the c3p0 connection pool reconnect with DB. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/JPA-consumer-reconnection-tp5775721p5775767.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
