[
https://issues.apache.org/jira/browse/ZOOKEEPER-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631887#action_12631887
]
Patrick Hunt commented on ZOOKEEPER-124:
----------------------------------------
I think there are 2 orthogonal issues here:
1) I believe you are having a problem in your (real) client code, I think it's
due to 137, dropping of events
2) however the test you created is broken, it will fail regardless of 137. the
problem is as I described, by closing the zk client when bang=false you will
lose events (those not yet delivered to the watchers).
I'm working on 1, you might try changing the test as I described and see if you
still see 2 (or just wait for the fix for 1...)
> 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.
