re delivery.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Logging-Error-in-Message-or-Exchange-in-DB-Not-getting-the-exception-in-Processor-tp5770526p5770528.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
C
okay, worked Like a Charm.
Just a question, the ErrorProcessor will be called once only after the
redelivery policy limit is exhausted I hope not for every re delivery.
--
View this message in context:
http://camel.465427.n5.nabble.com/Logging-Error-in-Message-or-Exchange-in-DB-Not-getting
Hi
See this FAQ
http://camel.apache.org/why-is-the-exception-null-when-i-use-onexception.html
On Mon, Aug 10, 2015 at 1:19 PM, Felix Thomas wrote:
> Hello,
>
> I tried the Below error Handling using DeadLetterChannel , but
> currently I am not getting the exception or error in my processor
Hello,
I tried the Below error Handling using DeadLetterChannel , but
currently I am not getting the exception or error in my processor . I want
to log in DB the message along with the reason it failed , for example JDBC
exception, Null pointer exception , data Validation exception in some