[
https://issues.apache.org/jira/browse/ZOOKEEPER-2707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15881605#comment-15881605
]
Abraham Fine commented on ZOOKEEPER-2707:
-----------------------------------------
This appears to be related to ZOOKEEPER-1858.
The problem looks like it comes from`Assert.assertEquals("Unexpected bean
exists!", 0, children.size());` in `ClientBase#verifyUnexpectedBeans` which I
think causes a race condition.
I think the first occurrence of this failure can be found here:
http://apache.markmail.org/thread/5nuvqfufpvkymlli dating 2/24/14 a month after
ZOOKEEPER-1858 was merged in.
I have been trying to reproduce locally but have not been successful yet.
I'm wondering how valuable this assertion is. Is this something we can just
remove or do we need to find a better solution?
Would appreciate your insight on this issue [~rakeshr].
> Fix "Unexpected bean exists!" issue in WatcherTests
> ---------------------------------------------------
>
> Key: ZOOKEEPER-2707
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2707
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: tests
> Affects Versions: 3.4.10, 3.5.3
> Reporter: Abraham Fine
> Assignee: Abraham Fine
>
> All the WatcherTests occasionally fail with:
> {code}
> Error Message:
> Unexpected bean exists! expected:<0> but was:<1>
> Stack Trace:
> junit.framework.AssertionFailedError: Unexpected bean exists! expected:<0>
> but was:<1>
> at
> org.apache.zookeeper.test.ClientBase.verifyUnexpectedBeans(ClientBase.java:498)
> at org.apache.zookeeper.test.ClientBase.startServer(ClientBase.java:477)
> at org.apache.zookeeper.test.ClientBase.setUp(ClientBase.java:460)
> at org.apache.zookeeper.test.WatcherTest.setUp(WatcherTest.java:76)
> {code}
> Here is an example:
> https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/422/
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
