You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2017/06/16 16:08:00 UTC

[jira] [Resolved] (KARAF-5192) Decanter collector should be able to filter some loggers

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

Jean-Baptiste Onofré resolved KARAF-5192.
-----------------------------------------
    Resolution: Fixed

> Decanter collector should be able to filter some loggers
> --------------------------------------------------------
>
>                 Key: KARAF-5192
>                 URL: https://issues.apache.org/jira/browse/KARAF-5192
>             Project: Karaf
>          Issue Type: Improvement
>          Components: decanter
>    Affects Versions: decanter-1.3.0
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>             Fix For: decanter-1.4.0
>
>
> When an appender (for instance elasticsearch or cassandra) can't send the collected data to the backend (for instance due to network issue), and the log collector is installed, we have an infinite loop: the appender throws an exception (a simple {{LOG.warn()}}), trapped by the log collector which tries to post the event,  creating the appender exception again, and so on.
> The Decanter appenders should set the {{inLogAppender}} MDC (filtered by the log collector) to avoid this infinite loop.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)