I suspect you have two exceptions propagating. One occurs in the main body of your route. This causes the onException block to trigger but immediately its bringing up the second exception when trying to process the telemetryFailureProcessor. The second is causing the the onException block to except itself. I would advise putting some trace system.out.println inside that processor, or better yet catching it in a debugger,and seeing if this is the issue. Why an older version of camel handled it is another question. From the route I cant see anything wrong so I suspect the problem is in the custom code. I dont know what behavior camel will have if you throw inside an onException block but I suspect something like you are seeing here.
*Robert Simmons Jr. MSc. - Lead Java Architect @ EA* *Author of: Hardcore Java (2003) and Maintainable Java (2012)* *LinkedIn: **http://www.linkedin.com/pub/robert-simmons/40/852/a39 <http://www.linkedin.com/pub/robert-simmons/40/852/a39>* On Wed, Dec 11, 2013 at 6:12 AM, jguerra <jg.gue...@gmail.com> wrote: > I posted to you both a copy of the whole camel.xml. It's a working copy on > Camel 2.7.0, but for some reason I got the problems described above on > Camel > 2.12.1. > Please feel free to contact me to get more information > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Problem-with-exception-handler-onException-on-Camel-2-12-X-routes-tp5742605p5744598.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
