[
https://issues.apache.org/jira/browse/SLING-11168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17502350#comment-17502350
]
Stefan Seifert commented on SLING-11168:
----------------------------------------
and i can confirm konrads assumption from [this
comment|https://issues.apache.org/jira/browse/SLING-11168?focusedCommentId=17500773#comment-17500773]
by adding some more logging to contentloader. at lot of bundles are handles
before actually the readers are registered - including
{{com.composum.nodes.commons}}. after they are registered, the other bundles,
including {{com.composum.nodes.console}} are handled.
will create a separate ticket, a fix should not be that difficult. still
wondering why it happens only in specific windows environments.
> Sling Starter 12: Unable to launch Composum
> -------------------------------------------
>
> Key: SLING-11168
> URL: https://issues.apache.org/jira/browse/SLING-11168
> Project: Sling
> Issue Type: Bug
> Components: Starter
> Affects Versions: Starter 12
> Reporter: Stefan Seifert
> Priority: Major
> Fix For: Starter 12
>
> Attachments: error.log, image-2022-03-01-17-47-08-965.png,
> screenshot-1.png, starter-12-windows.log
>
>
> environment:
> * Windows 10
> * java 11.0.13 2021-10-19 LTS
> * Sling Starter: https://github.com/apache/sling-org-apache-sling-starter
> started sling starter 12 (or actually 13-SNAPSHOT from current master branch)
> with:
> {noformat}
> mvn clean install
> java -jar target/dependency/org.apache.sling.feature.launcher.jar -f
> target/slingfeature-tmp/feature-oak_tar.json
> {noformat}
> when trying to access composum via http://localhost:8080/bin/browser.html i
> get the normal sling login (if not logged in already) and login as
> admin/admin.
> directly after this i see a blink of composum, which is replaced immediately
> with another composum login dialog:
> [^image-2022-03-01-17-47-08-965.png]
> [^error.log] from the instance
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
