curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bdumon <...@git.apache.org>
Subject [GitHub] curator pull request: CURATOR-157 Avoid stack traces on close
Date Mon, 16 Feb 2015 08:27:04 GMT
Github user bdumon commented on the pull request:

    https://github.com/apache/curator/pull/51#issuecomment-74473597
  
    I follow your reasoning, until the last event:
    
    T2: processBackgroundResult(event) gets called on a closed connection
    
    There is no connection closed by NodeCache or PathChildrenCache. The point of the patch
is that after NodeCache/PathChildrenCache.close() returns, they won't be making use of the
ZK connection anymore, so that CuratorFramework.close() can be called without causing stacktraces.


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