[
https://issues.apache.org/jira/browse/OAK-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976470#comment-14976470
]
Julian Reschke edited comment on OAK-3499 at 10/27/15 2:58 PM:
---------------------------------------------------------------
Yup, can be reproduced by commenting out the code that finds hardware
interfaces.
What happens here is that in that case, when the DocumentNodeStore
(setClusterId(1)) is initialized the second time, it won't be able to re-use
the existing ClusterNodeInfo, as the machineId (set to a random UUID) does not
match. That was indeed intentional.
We probably need to tune the test case in some way.
was (Author: reschke):
Yup, can be reproduced by commenting out the code that finds hardware
interfaces. Will investigate.
> Test failures when there is no network interface
> ------------------------------------------------
>
> Key: OAK-3499
> URL: https://issues.apache.org/jira/browse/OAK-3499
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, mongomk
> Reporter: Marcel Reutegger
> Assignee: Julian Reschke
> Priority: Minor
>
> There are test failures when no network interface is available.
> {noformat}
> Tests in error:
> purge(org.apache.jackrabbit.oak.plugins.document.CollisionTest): Configured
> cluster node id 1 already in use:
>
> inactiveClusterId(org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreTest):
> Configured cluster node id 2 already in use:
>
> purgeUnmergedBranch(org.apache.jackrabbit.oak.plugins.document.UnmergedBranchTest):
> Configured cluster node id 1 already in use:
> {noformat}
> I'm quite confident these used to work before.
> [~reschke], could this be caused by recent changes for OAK-3449?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
