Is this related to the asynchronous routing engine for jms producer introduced in camel 2.5? As it relates to exceptions "thrown" from that producer? You might try the test again disabling the asynchronous engine for the jms producer ( set ?synchronous=true) to see if the result changes. Just a thought.
http://camel.apache.org/asynchronous-routing-engine.html and http://camel.apache.org/asynchronous-processing.html -- View this message in context: http://camel.465427.n5.nabble.com/RE-Issue-with-route-specific-onException-and-jms-component-tp3317547p3400815.html Sent from the Camel - Users mailing list archive at Nabble.com.
