camel.465427.n5.nabble.com/Re-throwing-exception-tp5798653p5799110.html
Sent from the Camel - Users mailing list archive at Nabble.com.
You need to handle the exception with handled(true)
On Mon, May 8, 2017 at 4:31 PM, las wrote:
> Can I get a response?
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Re-throwing-exception-tp5798653p5799108.html
> Sent from the Camel - Us
Can I get a response?
--
View this message in context:
http://camel.465427.n5.nabble.com/Re-throwing-exception-tp5798653p5799108.html
Sent from the Camel - Users mailing list archive at Nabble.com.
or
failure.
--
View this message in context:
http://camel.465427.n5.nabble.com/Re-throwing-exception-tp5798653p5798771.html
Sent from the Camel - Users mailing list archive at Nabble.com.
NoErrorHandler is not working either.
onMessage processor throws an error and it's not getting propagated. The
exception/error gets added to the exchange and the route is always
successful.
--
View this message in context:
http://camel.465427.n5.nabble.com/Re-throwing-exce
onException(Exception.class).to("anotherProcessor");
>
>from("queue:a").bean("someBean").to("processor");
>}
>};
>
> The exception or error gets trapped by fatalfallbackerrorhandler and the
> route ends successfully.
>
>
>
oute ends successfully.
--
View this message in context:
http://camel.465427.n5.nabble.com/Re-throwing-exception-tp5798653.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Yeah we fixed this recently so the loop will break out sooner now.
Will be in the next release.
On Thu, Jul 30, 2015 at 2:17 PM, clinton wrote:
> I'm using Spring DSL
> I coded a "loop", to handle a retry situation.
> Once the function is complete, I wanted to break out, so I setup an
> exception
