Re: dealing with exceptions in onExceptions definitions
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 <dennisholu@xxxxxxxxx> wrote:
> 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 exception is not logged by direct:logerrors, as I wish. Any
> ideas how to safely implement this?
> .onException(UpdateException.class) //retries and logs the error
> .onException(IgnoredException.class) //saves the POJO and
> logs the error
> .process().body(Pojo.class, processor::update) //
> throws UpdateException
Camel in Action 2: https://www.manning.com/ibsen2