Well there must be some weird stuff in that jdbc driver and connection pool as we only close resultset/prepared statement, and after that does a commit on the connection, and that is where you get that exception.
I suggest you debug this on your end as you got the problem at hand, with that jdbc driver combo of yours. It works on our end with a different jdbc driver. On Tue, Aug 12, 2014 at 11:49 AM, A577127 <antoine.mat...@worldline.com> wrote: > With this new version I get the same SQLException, but now I get it with > every requests : INSERT with useHeadersAsParameters=true & false, and even > SELECT requests. > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-jdbc-snapshots-SQLException-tp5755058p5755097.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
