curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cammckenzie <...@git.apache.org>
Subject [GitHub] curator pull request #197: [CURATOR-367] Delay reconnect on session expired
Date Mon, 27 Feb 2017 23:19:36 GMT
Github user cammckenzie commented on a diff in the pull request:

    https://github.com/apache/curator/pull/197#discussion_r103338590
  
    --- Diff: curator-client/src/main/java/org/apache/curator/ConnectionState.java ---
    @@ -283,12 +300,19 @@ private boolean checkState(Event.KeeperState state, boolean wasConnected)
                 new EventTrace(state.toString(), tracer.get(), getSessionId()).commit();
             }
     
    -        if ( checkNewConnectionString && zooKeeper.hasNewConnectionString() )
    +        return isConnected;
    +    }
    +
    +    private void handleState(Event.KeeperState state)
    +    {
    +        if (state == Event.KeeperState.Expired)
    +        {
    +            handleExpiredSession();
    --- End diff --
    
    It gets handled in the handleState() method, which is called from process()


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message