You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Jordan Zimmerman (JIRA)" <ji...@apache.org> on 2013/04/28 16:02:15 UTC

[jira] [Resolved] (CURATOR-23) Calling markLost in ZookeeperClient does not propagate event to ConnectionStateListeners

     [ https://issues.apache.org/jira/browse/CURATOR-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jordan Zimmerman resolved CURATOR-23.
-------------------------------------

    Resolution: Won't Fix

This is being re-worked. markLost is going to be removed in favor of a better solution. Stay tuned...
                
> Calling markLost in ZookeeperClient does not propagate event to ConnectionStateListeners
> ----------------------------------------------------------------------------------------
>
>                 Key: CURATOR-23
>                 URL: https://issues.apache.org/jira/browse/CURATOR-23
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 2.0.1
>            Reporter: Ioannis Canellos
>            Assignee: Jordan Zimmerman
>         Attachments: marklost-testcase.patch
>
>
> I would expect that a calling curatorFramework.getZookeeperClient().markLost() would propagate a LOST event and then a RECONNECTED (once the client gets reconnected) event to the registered ConnectionStateListeners, which doesn't seem to happen.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira