You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2015/09/24 16:30:04 UTC

[jira] [Resolved] (OAK-3420) DocumentNodeStoreService fails to restart DocumentNodeStore

     [ https://issues.apache.org/jira/browse/OAK-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Reschke resolved OAK-3420.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.22

trunk: http://svn.apache.org/r1705055
1.2: http://svn.apache.org/r1705065
1.0: http://svn.apache.org/r1705069

> 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, 1.2.7, 1.0.22
>
>         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)