You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Rural Hunter <ru...@gmail.com> on 2014/03/26 02:50:33 UTC
Error handler to both logger and dead letter queue?
Hi,
I configured the error handler to send messages causing error to dead
letter queue. I noticed when the message went to the dead letter queue,
there is no error in the log. In this case, it's very hard for me to
know what's the problem with those messages. Is it possible for the
error handler to log the error/exception before sending the message to
dead letter queue?
Re: Error handler to both logger and dead letter queue?
Posted by Rural Hunter <ru...@gmail.com>.
oh, got it. thanks.
于 2014/3/28 13:59, Claus Ibsen 写道:
> The caused exception is stored as a property on the Exchange.
>
> See more details
> http://camel.apache.org/why-is-the-exception-null-when-i-use-onexception.html
>
> On Fri, Mar 28, 2014 at 6:31 AM, Rural Hunter <ru...@gmail.com> wrote:
>> I checked the doc and it seems only log the exchange but I actually want the
>> exception/error.
>>
>> 于 2014/3/27 18:43, Chirag Dewan 写道:
>>
>>> Hi,
>>>
>>> You can try the log component.
>>>
>>> http://camel.apache.org/log.html
>>>
>>> BR,
>>>
>>> Chirag
>>
>
>
Re: Error handler to both logger and dead letter queue?
Posted by Claus Ibsen <cl...@gmail.com>.
The caused exception is stored as a property on the Exchange.
See more details
http://camel.apache.org/why-is-the-exception-null-when-i-use-onexception.html
On Fri, Mar 28, 2014 at 6:31 AM, Rural Hunter <ru...@gmail.com> wrote:
> I checked the doc and it seems only log the exchange but I actually want the
> exception/error.
>
> 于 2014/3/27 18:43, Chirag Dewan 写道:
>
>> Hi,
>>
>> You can try the log component.
>>
>> http://camel.apache.org/log.html
>>
>> BR,
>>
>> Chirag
>
>
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Make your Camel applications look hawt, try: http://hawt.io
Re: Error handler to both logger and dead letter queue?
Posted by Rural Hunter <ru...@gmail.com>.
I checked the doc and it seems only log the exchange but I actually want
the exception/error.
于 2014/3/27 18:43, Chirag Dewan 写道:
> Hi,
>
> You can try the log component.
>
> http://camel.apache.org/log.html
>
> BR,
>
> Chirag
Re: Error handler to both logger and dead letter queue?
Posted by Chirag Dewan <ch...@yahoo.in>.
Hi,
You can try the log component.
http://camel.apache.org/log.html
BR,
Chirag
________________________________
From: Rural Hunter <ru...@gmail.com>
To: users@camel.apache.org
Sent: Wednesday, 26 March 2014 7:20 AM
Subject: Error handler to both logger and dead letter queue?
Hi,
I configured the error handler to send messages causing error to dead
letter queue. I noticed when the message went to the dead letter queue,
there is no error in the log. In this case, it's very hard for me to
know what's the problem with those messages. Is it possible for the
error handler to log the error/exception before sending the message to
dead letter queue?
Re: Error handler to both logger and dead letter queue?
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
You can use a direct endpoint as the DLQ and then have a route where
you route to a log and then the actual DQL you wanna use. eg its then
just a route and you can do what you want.
On Wed, Mar 26, 2014 at 2:50 AM, Rural Hunter <ru...@gmail.com> wrote:
> Hi,
>
> I configured the error handler to send messages causing error to dead letter
> queue. I noticed when the message went to the dead letter queue, there is no
> error in the log. In this case, it's very hard for me to know what's the
> problem with those messages. Is it possible for the error handler to log the
> error/exception before sending the message to dead letter queue?
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Make your Camel applications look hawt, try: http://hawt.io