Hi, I encountered the same trouble when I got SOAP fault.
The first processor in the onException route, I put "exchange.getOut().setBody(null)" , then multiple process worked. When onException route received SOAP fault, the outMessage already contains Exception info, that cause another Exception at the next process and rollback, I guess. -- View this message in context: http://camel.465427.n5.nabble.com/Does-onException-not-support-multiple-statements-tp4381958p4746297.html Sent from the Camel - Users mailing list archive at Nabble.com.
