You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Marco Crivellaro <ma...@gmail.com> on 2013/12/11 14:37:54 UTC
loggingErrorHandler formatting
how do I define the log format when using loggingErrorHandler?
I am interested in setting properties like: showExchangeId,
showExchangePattern, showBody... the default format is too verbose
--
View this message in context: http://camel.465427.n5.nabble.com/loggingErrorHandler-formatting-tp5744603.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: loggingErrorHandler formatting
Posted by Marco Crivellaro <ma...@gmail.com>.
I have tried the suggested approach but it doesn't seem to work like having a
DefaultErrorHandler; in my route there is an aggregator and once an exchange
runs in error the routing does not proceed to the step after the aggregation
if this runs in timeout.
--
View this message in context: http://camel.465427.n5.nabble.com/loggingErrorHandler-formatting-tp5744603p5744683.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: loggingErrorHandler formatting
Posted by Claus Ibsen <cl...@gmail.com>.
You cannot customize the logging.
Instead use dead letter channel and use a log endpoint as its
endpoint. Then you can configure what to show on the log endpoint.
http://camel.apache.org/log
On Wed, Dec 11, 2013 at 2:37 PM, Marco Crivellaro <ma...@gmail.com> wrote:
> how do I define the log format when using loggingErrorHandler?
> I am interested in setting properties like: showExchangeId,
> showExchangePattern, showBody... the default format is too verbose
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/loggingErrorHandler-formatting-tp5744603.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
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