You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2014/10/27 13:07:33 UTC

[jira] [Assigned] (CAMEL-7967) camel-rabbitmq logging exceptions as debug

     [ https://issues.apache.org/jira/browse/CAMEL-7967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang reassigned CAMEL-7967:
-----------------------------------

    Assignee: Willem Jiang

> camel-rabbitmq logging exceptions as debug
> ------------------------------------------
>
>                 Key: CAMEL-7967
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7967
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-rabbitmq
>    Affects Versions: 2.14.0
>            Reporter: Marco Crivellaro
>            Assignee: Willem Jiang
>
> 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. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)