Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
Commons Log 4.0.0
-
None
-
None
Description
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
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
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
Attachments
Issue Links
- is related to
-
SLING-3386 Enable support starting bundle in custom oreder at start level 1
- Resolved