curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <>
Subject [jira] [Reopened] (CURATOR-52) Callbacks are not called on retry-able errors
Date Tue, 10 Sep 2013 19:11:51 GMT


Jordan Zimmerman reopened CURATOR-52:

Per [~barkbay]:

"Unfortunately i'm still having "connection loss" events that are not
propagated to callbacks.

It happens when Curator call ConnectionState.checkTimeouts, if the
connection has been lost for Math.min(sessionTimeoutMs,
connectionTimeoutMs) then a ConnectionLoss exception is raised even if the
session has not actually expired (because the session timeout is far less
than connection timeout).
Here is a unit test :

The bad news is that since it is an exception (and not a "legacy" Zookeeper
event) it is handled by
CuratorFrameworkImpl.handleBackgroundOperationException that does not
propagate the event to the callback.

A workaround might be to add this kind of thing :
What are your thoughts on that?"
> Callbacks are not called on retry-able errors
> ---------------------------------------------
>                 Key: CURATOR-52
>                 URL:
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 2.2.0-incubating
>            Reporter: Michael Morello
>            Assignee: Jordan Zimmerman
>             Fix For: 2.2.1-incubating
>         Attachments: CURATOR-52.patch
not propagated to callback when the retry policy gave up if the operation is done in background.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message