Mailing-List: contact dev-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@curator.apache.org
From: tiny657 <git@git.apache.org>
To: dev@curator.apache.org
Reply-To: dev@curator.apache.org
References: <git-pr-27-curator@git.apache.org>
In-Reply-To: <git-pr-27-curator@git.apache.org>
Subject: [GitHub] curator pull request: fixed not to try to reconnect when
 session a...
Content-Type: text/plain
Message-Id: <20140801022052.F3FDA9BC220@tyr.zones.apache.org>
Date: Fri,  1 Aug 2014 02:20:52 +0000 (UTC)

Github user tiny657 commented on the pull request:

    https://github.com/apache/curator/pull/27#issuecomment-50842556
  
    I have a question.
    How do I watch the znode again when reconnected after connection and session timeout?
    I think the application didn't know RECONNECTED state. 
    Therefore the application didn't watch any change of the znode after that.
    
    [log]
    Connection attempt unsuccessful after 10205 (greater than max timeout of 10000). Resetting connection and trying again with a new connection.
    reset
    State change: RECONNECTED
    There are no ConnectionStateListeners registered.


---
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.
---