[
https://issues.apache.org/jira/browse/CURATOR-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912945#comment-13912945
]
Jordan Zimmerman commented on CURATOR-83:
-----------------------------------------
Please provide a test that shows this problem.
> LeaderLatch.close() doesn't fire LeaderLatchListener.notLeader()
> ----------------------------------------------------------------
>
> Key: CURATOR-83
> URL: https://issues.apache.org/jira/browse/CURATOR-83
> Project: Apache Curator
> Issue Type: Bug
> Components: Recipes
> Affects Versions: 2.3.0
> Reporter: Craig Muchinsky
>
> When closing a LeaderLatch, the order of cleanup is such that
> LeaderLatchListeners are not told they are no longer the leader. Within the
> finally block of the close() method the listener container is being cleared
> prior to the call to setLeadership(false). I believe simply reversing these
> calls will fix the problem.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
