curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CURATOR-181) discovery: registration of wrong/old service instance on RECONNECT
Date Mon, 12 Jan 2015 21:12:35 GMT

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

Jordan Zimmerman resolved CURATOR-181.
--------------------------------------
    Resolution: Fixed

> discovery: registration of wrong/old service instance on RECONNECT
> ------------------------------------------------------------------
>
>                 Key: CURATOR-181
>                 URL: https://issues.apache.org/jira/browse/CURATOR-181
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>            Reporter: Jordan Zimmerman
>            Assignee: Jordan Zimmerman
>             Fix For: 2.7.1
>
>
> PR without a Jira: https://github.com/apache/curator/pull/43
> ServiceDiscoveryImpl.registerService() remembers service registrations in a map. However
updateService() does not update the map. 
> This causes a wrong registration in the case of a RECONNECT - e.g. reRegisterServices()
called by the ConnectionStateListener registers the old ServiceInstance instead of the updated
one.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message