Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
The 'intruder' node timed out (on construction of the ReplicatedEnvironment with the following stack trace. The remainder of the group had already (correctly) shut themselves down in response to the unexpected node. It seem the ReplicaConsistencyException is another legitimate way the intruder node can fail, which, up until now the test didn't anticipate.
<error message="(JE 5.0.104) Unable to achieve consistency despite waiting for 300000 ms." type="com.sleepycat.je.rep.ReplicaConsistencyException"><![CDATA[com.sleepycat.je.rep.ReplicaConsistencyException: (JE 5.0.104) Unable to achieve consistency despite waiting for 300000 ms. at com.sleepycat.je.rep.impl.node.Replica$ConsistencyTracker.await(Replica.java:1396) at com.sleepycat.je.rep.impl.node.Replica$ConsistencyTracker.awaitVLSN(Replica.java:1372) at com.sleepycat.je.rep.impl.PointConsistencyPolicy.ensureConsistency(PointConsistencyPolicy.java:79) at com.sleepycat.je.rep.impl.node.RepNode.joinAsReplica(RepNode.java:1909) at com.sleepycat.je.rep.impl.node.RepNode.joinGroup(RepNode.java:1827) at com.sleepycat.je.rep.impl.RepImpl.joinGroup(RepImpl.java:506) at com.sleepycat.je.rep.ReplicatedEnvironment.joinGroup(ReplicatedEnvironment.java:479) at com.sleepycat.je.rep.ReplicatedEnvironment.<init>(ReplicatedEnvironment.java:532) at com.sleepycat.je.rep.ReplicatedEnvironment.<init>(ReplicatedEnvironment.java:397) at com.sleepycat.je.rep.ReplicatedEnvironment.<init>(ReplicatedEnvironment.java:461) at org.apache.qpid.server.store.berkeleydb.BDBHAVirtualHostNodeTest.joinIntruder(BDBHAVirtualHostNodeTest.java:821) at org.apache.qpid.server.store.berkeleydb.BDBHAVirtualHostNodeTest.testIntruderConnected(BDBHAVirtualHostNodeTest.java:795)