[
https://issues.apache.org/jira/browse/SLING-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476829#comment-13476829
]
Felix Meschberger commented on SLING-2622:
------------------------------------------
First stop-gap fix is sending the framework log messages through Sling's
MainDelegate logging to have consistent log message formatting (including
timestamps) and also serialized logging as much as possible.
Added a synchronized block (on out) around the actual log message writing in
the MainDelegate.log method to ensure concurrent log messages don't overlap and
thus garble the output.
Done in Rev. 1398686
> Framework does not log through the Sling Logging Infrastructure
> ---------------------------------------------------------------
>
> Key: SLING-2622
> URL: https://issues.apache.org/jira/browse/SLING-2622
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Affects Versions: Commons Log Service 1.0.0, Commons Log 3.0.0
> Reporter: Felix Meschberger
>
> When raising the log level to DEBUG on startup, the framework emits a lot of
> logging. Unfortunately this log goes to stdout instead of through the Sling
> Logging Infrastructure (probably the LogService would be good to use).
> This prevents capturing these messages for support.
--
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
