[
https://issues.apache.org/jira/browse/SLING-11168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501261#comment-17501261
]
Stefan Seifert commented on SLING-11168:
----------------------------------------
looks good! tested the branch on windows, composum console is working, the
problem is solved.
but: similar to the smoke test i experience the same problem directly after
startup: sling starter homepage is displayed, i can login, but clicking on
browser content leads to a HTTP 404. after waiting 15-30 seconds more loading
is completed and composum works as expected.
probably we should include the startup of composum in our startup check so the
start screen is not displayed before (is possible).
i've noticed another issue in sling 12: there is no "intermediate startup page"
that was displayed in sling 11 during startup when not all services are ready.
during startup i see only
{quote}
503 Service Unavailable
(Could not read 'content/content/startup/index.html' from bundle
'org.apache.sling.starter.content': file not found)
{quote}
> 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
> * 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)
