[jira] [Resolved] (SLING-3251) Enable Logback ChangeLevelDispatcher by default if JUL Integration is enabled

["Chetan Mehrotra (JIRA)" <ji...@apache.org>]

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

Chetan Mehrotra resolved SLING-3251.
------------------------------------

       Resolution: Fixed
    Fix Version/s: Commons Log 4.0.0

Added support in http://svn.apache.org/r1551120

With this Commons Log would install a {{LevelChangePropagator}} automatically if it detects that Slf4j Bridge Handler has to be enabled. This should make use of this feature more performant as otherwise  a bit of performance degradation would be observed for JUL logging [1]

[1] http://logback.qos.ch/manual/configuration.html#LevelChangePropagator

> Enable Logback ChangeLevelDispatcher by default if JUL Integration is enabled
> -----------------------------------------------------------------------------
>
>                 Key: SLING-3251
>                 URL: https://issues.apache.org/jira/browse/SLING-3251
>             Project: Sling
>          Issue Type: Improvement
>          Components: Commons
>    Affects Versions: Commons Log 4.0.0
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>             Fix For: Commons Log 4.0.0
>
>
> With Logback its possible to use ChangeLevelDispatcher [1] to minimize the performance impact. Currently one needs to explicitly enable in logback.xml via
> {code:xml}
> <configuration>
>   <contextListener class="ch.qos.logback.classic.jul.LevelChangePropagator"/>
> </configuration>
> {code}
> It would be better if Logback Integration logic adds this listener on its own if the {{org.apache.sling.commons.log.julenabled}} is set to true without requiring explicit user effort to tweak Logback xml config
> [1] http://logback.qos.ch/manual/configuration.html#LevelChangePropagator



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)