sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Munteanu (Jira)" <>
Subject [jira] [Commented] (SLING-9118) Sling fails to start when database exists but 'sling' directory is missing
Date Wed, 22 Apr 2020 16:51:00 GMT


Robert Munteanu commented on SLING-9118:

[~carlosmunoz] - we're using it extensively at Adobe, so it's definitely mature enough. I
think [~andysch] would be a good person to point you to how you can get started with Sling
and the Feature Model.

If you want to just launch Sling without packaging a jar you would need to run the provisioning
model to feature model converted and then use the feature model launcher.


If you want to build an executable jar as well, you should look into the kickstart launcher
as well


> Sling fails to start when database exists but 'sling' directory is missing
> --------------------------------------------------------------------------
>                 Key: SLING-9118
>                 URL:
>             Project: Sling
>          Issue Type: Bug
>            Reporter: Ben Radey
>            Assignee: Robert Munteanu
>            Priority: Major
>         Attachments:, error.log,,,,, sling-startup-error.log.txt
> # Create a persistent mongodb to use with Sling.
>  # Start sling using the mongodb.
>  # Stop sling.
>  # Remove 'sling' directory.
>  # Attempt to restart sling. Ultimately, sling fails to start.
> ----
> Steps to reproduce with attached scripts:
> # Run [^] . This creates a MongoDB 3.6 container named _mongo-sling_
> # Run [^]. This starts up Sling in the oak_mongo runmode, shuts it
down after it's (probably) started up
> # Run [^]. This moves away the sling directory and starts up a new
instance. This always fails
> For cleanup, the [^] script stops and removes the _mongo-sling_ container.

This message was sent by Atlassian Jira

View raw message