curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bdumon <>
Subject [GitHub] curator pull request: CURATOR-157 Avoid stack traces on close
Date Thu, 19 Feb 2015 11:21:41 GMT
Github user bdumon commented on the pull request:
    In those stack traces, it is CuratorFramework/CuratorZookeeperClient which check if their
state is started (which is stil true, since we have not closed them, we have closed the cache),
not NodeCache/PathChildrenCache.
    Or are you referring to something else?

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 or file a JIRA ticket
with INFRA.

View raw message