; > > > logs the error
> > > > .handled(true)
> > > > .process().body(Pojo.class, processor::update) //
> > > > throws UpdateException
> > > > .to(direct:logerrors)
> > > > .end()
> > logs the error
> > > .handled(true)
> > > .process().body(Pojo.class, processor::update) //
> > > throws UpdateException
> > > .to(direct:logerrors)
> > > .end()
> > &g
.to(direct:logerrors)
> > .end()
> >
> > Regards,
> > Dan
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
>
> __
Hi
This is by design, to avoid circular onException to trigger in endless.
So try to design your error handling in a more safe manner
On Tue, Nov 13, 2018 at 10:23 AM Dennis Holunder wrote:
>
> Hello,
>
> I have two onException definitions which catch exceptions and send
> them to
Hello,
I have two onException definitions which catch exceptions and send
them to direct:logerrors endpoint. The second exception might throw an
exception which should be caught and handled by the first one. But
this doesn't work. The FatalFallbackErrorHandler kicks in and as the
result the
