Genius! You appear to be absolutely correct. I've been meaning to come back to this to log a bug properly, so thanks for the kick.
My earlier JUnit test I attached now passes with ?synchronous=true on the JMS endpoint; and of course explains why I could not replicate the behaviour with non-JMS endpoints. Which leads to the further question - is this still a bug? Why with the Asynchronous Routing Engine does the exception bubble up to the "parent" route? -- View this message in context: http://camel.465427.n5.nabble.com/RE-Issue-with-route-specific-onException-and-jms-component-tp3317547p3402793.html Sent from the Camel - Users mailing list archive at Nabble.com.
