[jira] [Commented] (SLING-11168) Sling Starter 12: Unable to launch Composum

["Hans-Peter Stoerr (Jira)" <ji...@apache.org>]

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

Hans-Peter Stoerr commented on SLING-11168:
-------------------------------------------

Hi!
It's a pity that the content loader upgrade to 2.5.2 didn't actually make it into Sling Starter 12. I didn't get this problem when running the starter locally just as a jar, but I get the error once in a couple of starts when the starter is launched in a docker image in an integration test, and can reliably reproduce it repeating that like this:
{code:java}
while mvn clean install; do sleep 1; done{code}
Hopefully there will be a Sling Starter 13 or 12.1 that includes that in the nearer future?

By the way - it was an interesting challenge to find out the cause of such a kind of failure, since the browser wasn't available to see the problem. I was wondering whether using the [oak-run|https://jackrabbit.apache.org/oak/docs/command_line.html] tool
{code:java}
java -mx4g -jar oak-run-1.42.0.jar explore launcher/repository/segmentstore/{code}
would help me to find the problem, but then remembered that the Composum Browser has a newer feature of "mounting" a remote repository for debugging purposes with the Composum Remote Resource Provider configuration, which works by accessing the repository of the Sling Starter instance that needs debugging through requests like /content/something.1.json , which made that considerably easier.
Thanks for all that good work!

> 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
>            Assignee: 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
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> 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)