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 2014/02/24 14:39:21 UTC

[jira] [Commented] (SLING-3410) Log the Logback initialization related logs to normal log for transient errors

    [ https://issues.apache.org/jira/browse/SLING-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910302#comment-13910302 ] 

Chetan Mehrotra commented on SLING-3410:
----------------------------------------

Added support in r1571283 and r1571284

Now in case transient issues are observed in Logback status then those logs would be routed to normal logs and a marker '\*Logback Status\*' would be added to line as shown below.

In case Logback was not successfully initialized then this marker would not be added. 

{noformat}
19:01:05,627 *Logback Status* |-WARN in org.apache.sling.commons.log.logback.internal.LogbackManager@6563068f - Context: sling reloaded.
19:01:05,631 *Logback Status* |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set
{noformat}

> Log the Logback initialization related logs to normal log for transient errors
> ------------------------------------------------------------------------------
>
>                 Key: SLING-3410
>                 URL: https://issues.apache.org/jira/browse/SLING-3410
>             Project: Sling
>          Issue Type: Improvement
>          Components: Commons
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>             Fix For: Commons Log 4.0.0
>
>
> Currently Sling Log would dump Logback status message to system out in case some warning/error are observed in Logback initialization. If the overall Logback initialization is successful then these logs should be logged as part of normal logging flow



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)