[
https://issues.apache.org/jira/browse/QPID-7059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143174#comment-15143174
]
Keith Wall commented on QPID-7059:
----------------------------------
This is the first time we have seen this failure occur.
The Java Broker populates the joinTime of the remote node from from from JE
DbPing it it appears that in this situation the value came back as 0, even
though we know the node had already gone into either MASTER or REPLICA. The
Java Broker's coding looks thread safe.
If this were to happen to a production user, impact would be minimal. The
attribute is displayed for informational purposes, and there is no
functionality depends on it. In addition the view is refreshed each time the
remote node is pinged, so if they were to be a transient problem, the value
should update itself on the next cycle.
If this test failure where to be seen again, we could consider some defensive
coding in BDBHAVirtualHostNodeImpl.java:1146.
> BDBHAVirtualHostNodeRestTest.testDeleteMasterNode failed sporadically on
> Apache CI
> ----------------------------------------------------------------------------------
>
> Key: QPID-7059
> URL: https://issues.apache.org/jira/browse/QPID-7059
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Keith Wall
> Priority: Minor
>
> The following test was seen to fail on Apache CI:
> https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-BDB-TestMatrix/jdk=JDK%201.7%20(latest),label=Ubuntu,profile=java-bdb.0-10/2122/testReport/junit/org.apache.qpid.server.store.berkeleydb.replication/BDBHAVirtualHostNodeRestTest/testDeleteMasterNode/
> The test verifies that the remote view of the other nodes in the group is
> populated. In this case the test failed because the node's join time is
> recorded as zero.
> {noformat}
> org.apache.qpid.server.store.berkeleydb.replication.BDBHAVirtualHostNodeRestTest.testDeleteMasterNode
> Failing for the past 1 build (Since Failed#2122 )
> Took 10 sec.
> add description
> Error Message
> Node node2 has unexpected joinTime 0
> Stacktrace
> junit.framework.AssertionFailedError: Node node2 has unexpected joinTime 0
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at
> org.apache.qpid.server.store.berkeleydb.replication.BDBHAVirtualHostNodeRestTest.assertRemoteNodeData(BDBHAVirtualHostNodeRestTest.java:412)
> at
> org.apache.qpid.server.store.berkeleydb.replication.BDBHAVirtualHostNodeRestTest.assertRemoteNodes(BDBHAVirtualHostNodeRestTest.java:397)
> at
> org.apache.qpid.server.store.berkeleydb.replication.BDBHAVirtualHostNodeRestTest.testDeleteMasterNode(BDBHAVirtualHostNodeRestTest.java:206)
> {noformat}
> There were no further errors in the logs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
