I have a simply use case which uses the quartz jdbc component. We've tested both Oracle and MySQL with the same results.

Essentially, the first time the route runs, it works fine. The second time, it fails. There's not a lot of information as to why it failed and it appears to be in some sort of loop:

bluebird:QuartzTest sjavurek$ grep -c " DEBUG checkoutStatement: com.mchange.v2.c3p0.stmt.PerConnectionMaxOnlyStatementCache stats -- total size: 16;" nohup-failed.out 
4
bluebird:QuartzTest sjavurek$ grep -c " DEBUG checkoutStatement: com.mchange.v2.c3p0.stmt.PerConnectionMaxOnlyStatementCache stats -- total size: 16;" nohup-good.out 
1

Resetting the tables works. This fails in this manner using 2.13.0, however, 2.13.1 is working ok.

Can we identify the change so I can get a patch?