[
https://issues.apache.org/jira/browse/SLING-11168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17499878#comment-17499878
]
Sergiu Dumitriu commented on SLING-11168:
-----------------------------------------
It usually happens to the one dev that uses Windows on my team, but I have seen
it a couple of times on my Linux as well. I have no idea why it would behave so
different on Windows, since Java is supposed to be very platform-independent,
but here's something of interest: on the same Windows machine, most of the time
content loading happens before the repoinit is executed, so ACLs embedded in
source json files fail because the users they reference haven't been created
yet. May be an unrelated bug, or it may also be the cause of the composum
failure. Just my 2 cents.
> 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
> 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
> 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)
