[
https://issues.apache.org/jira/browse/SLING-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088818#comment-17088818
]
Robert Munteanu commented on SLING-9118:
----------------------------------------
[~carlosmunoz] - not at the moment, I'll let you know as soon as I have
something to test.
For the record, I've exprimented with eliminating the interrupt call from the
{{AbstractSlingRepositoryManager}}, and allowing the startup to proceeed, and
then shutting down the component. This exposes another problem - namely that
the components are started before all configurations are applied. Therefore as
soon as the {{DocumentNodeStore}} configuration is applied, the repository is
started, before even having the information about the login admin whitelist.
This leads to the repository startup concluding, but failing all left and right
due to that missing configuration.
Not sure that I have a solution for that. At this point I'm considering two
other options:
- adding some dampening to {{OakSlingRepositoryManager}} to make sure it is not
affected by start/stop sequences
- suggesting a change in Oak so that the {{SecurityProviderRegistration}}
requires a configuration policy
Of course, the longer-term solution is switching to the feature model, which
would remove all of these workarounds. But I don't see that happening on the
short term.
> Sling fails to start when database exists but 'sling' directory is missing
> --------------------------------------------------------------------------
>
> Key: SLING-9118
> URL: https://issues.apache.org/jira/browse/SLING-9118
> Project: Sling
> Issue Type: Bug
> Reporter: Ben Radey
> Assignee: Robert Munteanu
> Priority: Major
> Attachments: drop-mongo.sh, error.log, recreateSlingReplicaSet.sh,
> run-mongo.sh, run-sling-initial.sh, run-sling-second.sh,
> 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 [^run-mongo.sh] . This creates a MongoDB 3.6 container named
> _mongo-sling_
> # Run [^run-sling-initial.sh]. This starts up Sling in the oak_mongo runmode,
> shuts it down after it's (probably) started up
> # Run [^run-sling-second.sh]. This moves away the sling directory and starts
> up a new instance. This always fails
> For cleanup, the [^drop-mongo.sh] script stops and removes the _mongo-sling_
> container.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
