Yes, you are right as far I can see. it's correct that there is a double exception inside of the telemetryFailureProcessor when the message is not valid **but** when the message is valid, the exception still comes up!. Even though the processor is removed from the route, the java.sql.SQLException is not being caught. My hunch is that the exceptions are not even caught by the onException handler!.
-- View this message in context: http://camel.465427.n5.nabble.com/Problem-with-exception-handler-onException-on-Camel-2-12-X-routes-tp5742605p5744626.html Sent from the Camel - Users mailing list archive at Nabble.com.
