[
https://issues.apache.org/jira/browse/OAK-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14906341#comment-14906341
]
Julian Reschke commented on OAK-3420:
-------------------------------------
for now applying a simple fix that just avoids any attempts of restarting; this
at least avoids the NPE we've had before (which may indicate an attempt to
start a DocumentNodeStore that may not get disposed again)
> DocumentNodeStoreService fails to restart DocumentNodeStore
> -----------------------------------------------------------
>
> Key: OAK-3420
> URL: https://issues.apache.org/jira/browse/OAK-3420
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, mongomk, rdbmk
> Affects Versions: 1.0.21, 1.3.6, 1.2.6
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Labels: resilience
> Fix For: 1.3.7
>
> Attachments: DocumentNodeStoreConfigTest.groovy
>
>
> Scenario (test case will follow):
> 1) service configured for RDBDocumentStore with DataSources
> 2) gets started
> 3) DataSource unregisters, DocumentNodeStore gets shut down
> 4) DataSource is registered again
> 5) restart of DocumentNodeStore fails with NPE because at least one required
> component (executor?) now is null
> We need to decide whether this is a scenario that should be supported or not.
> If yes, we need to fix it. If no, we need to make the code more robust and
> improve diagnostics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)