You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2015/07/27 11:11:04 UTC

[jira] [Resolved] (SLING-4839) Allow to configure logger additivity via OSGi Config UI

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

Chetan Mehrotra resolved SLING-4839.
------------------------------------
    Resolution: Fixed

Done in http://svn.apache.org/r1692840

Both Log WebConsole plugin and OSGi config now provide support for configuring additivity

> Allow to configure logger additivity via OSGi Config UI
> -------------------------------------------------------
>
>                 Key: SLING-4839
>                 URL: https://issues.apache.org/jira/browse/SLING-4839
>             Project: Sling
>          Issue Type: Improvement
>          Components: Commons
>    Affects Versions: Commons Log 4.0.2
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>             Fix For: Commons Log 4.0.4
>
>
> While configuring the loggers via OSGi Commons Log sets the additivity to false by default. Due to this logs from those categories are not routed to main error log. This at times causes important exceptions from getting noticed and hence might get missed out.
> Commons Log does support controlling the additivity via OSGi config but that setting is not exposed in UI. This setting should be exposed via UI



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