Stu Hood commented on ZOOKEEPER-124:

I understand that a watch can only ever being triggered once and that only one 
watch can exist per client and znode. But I'm not sure how it is relevant to 
this test: each znode in the test is created with 
CreateMode.PERSISTENT_SEQUENTIAL, so multiple threads adding watches should 
never result in the condition you mentioned.


> 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.

Reply via email to