[
https://issues.apache.org/jira/browse/SLING-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated SLING-3045:
-----------------------------------
Attachment: SLING-3045.patch
Logback would log a warning if no appender is found when a log message is
received. During reset there is a small window where no appenders would be
present and such a warning is fine.
LogbackManager accounts for such scenario by recording the time
'resetStartTime' at which reset happened. By that time it ensures a default
console appender is attached to root. It only logs the warning if such a
message is found *after* resetStartTime. However its possible that in same
millisecond a log message arrives so suh filtering would fail.
To account for that we now add a millisecond extra so as to ensure the
'resetStartTime' reflects the time by which a console appender has been
attached to the root logger. Any warn message after the resetStartTime would
trigger log at console
Also set the default log level for root logger to INFO
> [logback]Warning logs logged for 'No appenders present in context [sling] for
> logger'
> -------------------------------------------------------------------------------------
>
> Key: SLING-3045
> URL: https://issues.apache.org/jira/browse/SLING-3045
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Affects Versions: Commons Log 4.0.0
> Reporter: Chetan Mehrotra
> Priority: Minor
> Attachments: SLING-3045.patch
>
>
> During system startup at times following warning is seen
> ---
> 14:48:24,969 |-WARN in
> Logger[org.apache.sling.installer.core.impl.OsgiInstallerImpl] - No appenders
> present in context [sling] for logger
> [org.apache.sling.installer.core.impl.OsgiInstallerImpl].
> ---
> Further some debug level logs are also seen during the startup
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
