camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: camel-rabbitmq logging exceptions as debug
Date Mon, 27 Oct 2014 08:11:44 GMT
Hi

Yeah that sounds like we should improve this. Feel free to log a JIRA ticket
http://camel.apache.org/support

On Thu, Oct 23, 2014 at 11:08 AM, Marco Crivellaro
<marco.crive@gmail.com> wrote:
> Hi,
> I am using Camel 2.14.0
> Connecting to RabbitMQ using camel-rabbitmq I've noticed that no ERROR is
> logged if the component cannot connect, the exceptions are handled and
> logged as DEBUG.
> This is a bit inconvenient as logging all DEBUG messages for the component
> fills up our logs, in production we usually set INFO as threshold.
>
> Is there any way of changing the logging level or be notified if the
> component cannot connect?
>
> ActiveMQ component does not have this issue (at least on Camel 2.8.x which
> we are using in production).
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/camel-rabbitmq-logging-exceptions-as-debug-tp5757936.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
hawtio: http://hawt.io/
fabric8: http://fabric8.io/

Mime
View raw message