[
https://issues.apache.org/jira/browse/SLING-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476825#comment-13476825
]
Felix Meschberger commented on SLING-2622:
------------------------------------------
Reason is that as of FELIX-536 (Framework 1.0.4) the framework disabled support
for LogService logging due to deadlock situations (mainly on startup).
For Sling we have to find a different solution, probably implementing our own
extension of the Felix Logger as we did for the Servlet Container integration
which logs to the servlet container (through the ServletContext).
> 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
