Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
Starter 12
-
None
-
Java 11 and 13 on MacOS
Description
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!