[jira] [Reopened] (CURATOR-52) Callbacks are not called on retry-able errors

["Jordan Zimmerman (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CURATOR-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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 : https://gist.github.com/barkbay/6507997

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 :
https://gist.github.com/barkbay/6507963
What are your thoughts on that?"
                
> Callbacks are not called on retry-able errors
> ---------------------------------------------
>
>                 Key: CURATOR-52
>                 URL: https://issues.apache.org/jira/browse/CURATOR-52
>             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
>
>
> Retry-able errors (CONNECTIONLOSS, OPERATIONTIMEOUT, SESSIONMOVED, SESSIONEXPIRED) are 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: http://www.atlassian.com/software/jira