[
https://issues.apache.org/jira/browse/ZOOKEEPER-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahadev konar updated ZOOKEEPER-204:
------------------------------------
Attachment: ZOOKEEPER-204.patch
made a few changes regarding logging and formatting .... otherwise +1
> SetWatches needs to be the first message after auth messages to the server
> --------------------------------------------------------------------------
>
> Key: ZOOKEEPER-204
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-204
> Project: Zookeeper
> Issue Type: Bug
> Components: java client
> Affects Versions: 3.0.0
> Reporter: Benjamin Reed
> Assignee: Benjamin Reed
> Fix For: 3.0.1, 3.1.0
>
> Attachments: ZOOKEEPER-204.patch, ZOOKEEPER-204.patch,
> ZOOKEEPER-204.patch, ZOOKEEPER-204.patch
>
>
> When the ZooKeeper java client makes a connection it queues a SetWatches
> request. The problem is that it puts the request at the end of the outgoing
> requests. This means that watches for requests that were queued before the
> connection is made and after the disconnect may improperly get their watches
> triggered.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
