sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chetan Mehrotra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-3340) Warnings on startup regarding no-op loggers
Date Mon, 03 Feb 2014 06:14:08 GMT

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

Chetan Mehrotra commented on SLING-3340:
----------------------------------------

Opened bug in Slf4j [1] and sent a pull request for the possible fix [2]

[1] http://bugzilla.slf4j.org/show_bug.cgi?id=311
[2] https://github.com/qos-ch/slf4j/pull/58

> Warnings on startup regarding no-op loggers
> -------------------------------------------
>
>                 Key: SLING-3340
>                 URL: https://issues.apache.org/jira/browse/SLING-3340
>             Project: Sling
>          Issue Type: Bug
>          Components: Commons
>    Affects Versions: Commons Log 4.0.0
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>
> Depening on the order in which bundles are installed Slf4j might use NoOp loggers for
loggers created before Logback is initialized. One would see a warning log like below
> {noformat}
> Slf4j is not initialized yet. Delaying Logback support initialization
> SLF4J: The following loggers will not work because they were created
> SLF4J: during the default configuration phase of the underlying logging system.
> SLF4J: See also http://www.slf4j.org/codes.html#substituteLogger
> SLF4J: org.apache.sling.commons.logservice
> SLF4J: org.apache.sling.installer.core
> SLF4J: org.apache.sling.installer.core.impl.OsgiInstallerImpl
> SLF4J: org.apache.sling.audit.osgi.installer
> SLF4J: org.apache.sling.installer.core.impl.PersistentResourceList
> SLF4J: org.apache.sling.installer.core.impl.EntityResourceList
> SLF4J: org.apache.sling.installer.core.impl.tasks.BundleTaskCreator
> SLF4J: org.apache.sling.installer.core.impl.DefaultTransformer
> SLF4J: org.apache.sling.installer.provider.file
> SLF4J: org.apache.sling.installer.provider.file.impl.ServicesListener
> SLF4J: org.apache.sling.installer.provider.file.impl.FileInstaller
> SLF4J: org.apache.sling.javax.activation
> SLF4J: org.apache.sling.javax.activation.internal.Activator
> SLF4J: org.apache.sling.javax.activation.internal.OsgiMailcapCommandMap
> SLF4J: org.apache.sling.launchpad.installer
> SLF4J: org.apache.sling.settings
> SLF4J: org.apache.sling.settings.impl.SlingSettingsServiceImpl
> SLF4J: org.apache.sling.launchpad.installer.impl.LaunchpadConfigInstaller
> SLF4J: org.apache.sling.installer.core.impl.tasks.RestartActiveBundlesTask
> {noformat}
> Given that log from Sling installer category are important and should not be lost we
should avoid such scenario to be created.
> See thread http://markmail.org/thread/n4zyj5akkh24ahh5



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

Mime
View raw message