You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (Jira)" <ji...@apache.org> on 2020/10/01 11:39:00 UTC
[jira] [Resolved] (SLING-9780) Log service missing after switching
to the feature model
[ https://issues.apache.org/jira/browse/SLING-9780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu resolved SLING-9780.
------------------------------------
Resolution: Fixed
Fixed with [sling-org-apache-sling-starter commit 8e5075d|https://github.com/apache/sling-org-apache-sling-starter/commit/8e5075d].
[~hanspeterstoerr] - can you please check?
> Log service missing after switching to the feature model
> --------------------------------------------------------
>
> 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
> Assignee: Robert Munteanu
> Priority: Minor
> Fix For: Starter 12
>
> Attachments: LogserviceNotRunning.png, Starter11-HasLogService.png, Starter12-NoLogService.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)