[
https://issues.apache.org/jira/browse/ZOOKEEPER-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631851#action_12631851
]
Patrick Hunt commented on ZOOKEEPER-124:
----------------------------------------
Stu, btw. You do know that if you call something like:
watcher = new watcher();
zk.exists("/foo", watcher); // sync or async doesn't matter
zk.exists("/foo", watcher);
zk.exists("/foo", watcher);
that only a single event will ever come back to the watcher, correct? I mean
that we don't store duplicates (where the node name and watcher together define
uniqueness).
Of course
zk.exists("/foo, new watcher()); // sync or async doesn't matter
zk.exists("/foo", new watcher());
zk.exists("/foo", new watcher());
would result in three events triggered on the client (one for each unique
watcher)
> StatCallback is broken in trunk
> -------------------------------
>
> Key: ZOOKEEPER-124
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-124
> Project: Zookeeper
> Issue Type: Bug
> Components: java client, server, tests
> Environment: Linux corner-cube 2.6.24-19-generic #1 SMP Fri Jul 11
> 23:41:49 UTC 2008 i686 GNU/Linux
> java version "1.6.0_06"
> Java(TM) SE Runtime Environment (build 1.6.0_06-b02)
> Java HotSpot(TM) Client VM (build 10.0-b22, mixed mode, sharing)
> Reporter: Stu Hood
> Assignee: Patrick Hunt
> Fix For: 3.0.0
>
> Attachments: stat-callback-fail-test.diff, stat-callback-test.diff
>
>
> StatCallback appears to be broken in trunk. I'll attach a patch for AsyncTest
> that triggers the behaviour.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
