[
https://issues.apache.org/jira/browse/SLING-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17062424#comment-17062424
]
Robert Munteanu commented on SLING-9118:
----------------------------------------
[~carlosmunoz] identified
https://github.com/apache/sling-org-apache-sling-starter/commit/bb1e10d97f3c163fb87917ea782afff674050891
as the offending commit. This upgrades {{o.a.s.jcr.base}} from 3.0.4 to 3.0.6.
The commit range is
https://github.com/apache/sling-org-apache-sling-jcr-base/compare/ec4a0d1ae0fe6b1e77c0c159ce178de7cba06488...5b3a4427b711cfcbdc86631b4bf12871beb06728
and contains the following Jira issues:
- SLING-7167
- SLING-7162
- SLING-7214
- SLING-7123
- SLING-7604
- SLING-7811
- SLING-8139
- SLING-8140
Next steps would be to identify which commit(s) actually caused the problem.
> 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
> Priority: Major
>
> # 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
