jira-importer commented on issue #573: URL: https://github.com/apache/curator/issues/573#issuecomment-2604698863
<i><a href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=randgalt";>randgalt</a>:</i> <p>Per <a href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=barkbay"; class="user-hover" rel="barkbay">Michael Morello</a>:</p> <p>"Unfortunately i'm still having "connection loss" events that are not<br/> propagated to callbacks.</p> <p>It happens when Curator call ConnectionState.checkTimeouts, if the<br/> connection has been lost for Math.min(sessionTimeoutMs,<br/> connectionTimeoutMs) then a ConnectionLoss exception is raised even if the<br/> session has not actually expired (because the session timeout is far less<br/> than connection timeout).<br/> Here is a unit test : <a href="https://gist.github.com/barkbay/6507997"; class="external-link" target="_blank" rel="nofollow noopener">https://gist.github.com/barkbay/6507997</a></p> <p>The bad news is that since it is an exception (and not a "legacy" Zookeeper<br/> event) it is handled by<br/> CuratorFrameworkImpl.handleBackgroundOperationException that does not<br/> propagate the event to the callback.</p> <p>A workaround might be to add this kind of thing :<br/> <a href="https://gist.github.com/barkbay/6507963"; class="external-link" target="_blank" rel="nofollow noopener">https://gist.github.com/barkbay/6507963</a><br/> What are your thoughts on that?"</p> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@curator.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
