You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Hans-Peter Stoerr (Jira)" <ji...@apache.org> on 2020/10/01 11:13:00 UTC
[jira] [Updated] (SLING-9780) Sling Starter 12: OSGI Log Service
does not work properly
[ https://issues.apache.org/jira/browse/SLING-9780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hans-Peter Stoerr updated SLING-9780:
-------------------------------------
Attachment: Screenshot 2020-10-01 at 12.18.18.png
> Sling Starter 12: OSGI Log Service does not work properly
> ---------------------------------------------------------
>
> Key: SLING-9780
> URL: https://issues.apache.org/jira/browse/SLING-9780
> Project: Sling
> Issue Type: Bug
> Components: Starter
> Affects Versions: Starter 12
> Environment: Java 11 and 13 on MacOS
> Reporter: Hans-Peter Stoerr
> Priority: Minor
> Attachments: Screenshot 2020-10-01 at 12.18.18.png
>
>
> In the current Sling Starter 12 snapshot the OSGI Log Service does not work properly. This has the effect that in the console at OSGI / Log Service [http://localhost:8080/system/console/logs] there is only the display "Log Service is not installed/running." and messages from OSGI (such as errors in activation methods) are inconveniently logged to stdout instead of the configured logfiles like error.log, which gave me some headache until I noticed that. :) Both the console plugin and the logging to error.log do work properly in version 11.
> This is in spite of the bundle org.apache.sling.commons.logservice being active. I tried downgrading it from the currently included 1.1.0 to 1.0.6, which works in the version 11 of the Sling Starter, but this doesn't help. So I guess it's some kind of configuration problem.
> Thanks so much for your amazing work!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)