[
https://issues.apache.org/jira/browse/OAK-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814931#comment-15814931
]
Julian Reschke edited comment on OAK-5098 at 2/8/17 12:27 PM:
--------------------------------------------------------------
FWIW, I just tried backporting this to 1.2. It patch applies cleanly, but for
some reason the new test case fails; it might rely on other changes in the
DocumentNodeStoreService which haven't been backported yet.
EDIT: apparently caused by the lack of other changes in the test framework...
was (Author: reschke):
FWIW, I just tried backporting this to 1.2. It patch applies cleanly, but for
some reason the new test case fails; it might rely on other changes in the
DocumentNodeStoreService which haven't been backported yet.
> improve DocumentNodeStoreService robustness for RDB configs
> -----------------------------------------------------------
>
> Key: OAK-5098
> URL: https://issues.apache.org/jira/browse/OAK-5098
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: documentmk, rdbmk
> Affects Versions: 1.5.14
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Labels: candidate_oak_1_0, candidate_oak_1_2, patch-available,
> resilience
> Fix For: 1.4.12, 1.5.15, 1.6.0
>
> Attachments: OAK-5098.diff
>
>
> It appears that very strange things can happen when the system isn't
> configured properly, for instance when multiple DataSources with the same
> name are configured.
> TODO:
> - log.info unbindDataSource() calls
> - prevent registrations of multiple node stores when bindDataSource() is
> called multiple times
> - in unbindDataSource(), check that the datasource is actually the one that
> was bound before
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
