Claus Ibsen-2 wrote: > > So where does your exception occur? > > And where do you expect Camel to react? >
The exception is engineered by the test to occur inside the JMS Component when trying to establish a connection to an invalid host. While my test case uses the TIBCO connection factory, the ActiveMQ one does the same, and I'm sure other exceptions at the JMS endpoint (A+A errors, topic/queue doesn't exist, etc) cause similar behaviour. I expect Camel to catch the exception and pass it to the handler inside the secondary route (the one starting with direct:secondaryEntry) since it has a blanket onException(Exception.class) handler. Thus the message should be redirected (in my test) to mock:secondaryErrors - not bubbling back up to the primary route and going to mock:mainErrors, as it currently is, without touching the secondary route's error handler at all. I can't work out in exactly which circumstances this is an issue - I think it's something to do with either the recipient list or the jms component or interaction between the two, as if I change the route to throw exceptions from other stages in the secondary route they seem to be handled correctly inside that route. Cheers - hope you're all having a good holiday break :) Chad -- View this message in context: http://camel.465427.n5.nabble.com/RE-Issue-with-route-specific-onException-and-jms-component-tp3317547p3319043.html Sent from the Camel - Users mailing list archive at Nabble.com.
