[ 
https://issues.apache.org/jira/browse/SLING-9780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17205373#comment-17205373
 ] 

Robert Munteanu commented on SLING-9780:
----------------------------------------

Thank you for the report. I tried this with the latest version of the Starter 
and Java 11, and it worked (mostly) as expected for me.

{noformat}
$ git describe 
org.apache.sling.starter-11-170-g3be467a
$ java -version
openjdk version "11.0.8" 2020-07-14
OpenJDK Runtime Environment (build 11.0.8+10-suse-1.3-x8664)
OpenJDK 64-Bit Server VM (build 11.0.8+10-suse-1.3-x8664, mixed mode)
$ java -jar target/dependency/org.apache.sling.feature.launcher.jar -f 
target/slingfeature-tmp/feature-oak_tar.json
{noformat}

Note that there are still some log messages printed on the console, until the 
log service is configured, but eventually {{launcher/error.log}} is created. Do 
you not have that file at all? If not, please attach the terminal output, maybe 
there is something there.

As for the web console, I get working output from 
http://localhost:8080/system/console/slinglog , but not 
http://localhost:8080/system/console/logs . Does this match your situation?

> 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
>
> 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)

Reply via email to