curator-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sakthipriyan Vairamani <sakthiprofessio...@gmail.com>
Subject Re: Error handling in background calls
Date Thu, 21 Jul 2016 02:49:24 GMT
Yes. That's exactly what I have. But the handler is not getting invoked at
all.

I am trying to get data from a node which doesn't exist yet, in background.
How will the program be notified of the error?

On 21-Jul-2016 12:55 AM, "Jordan Zimmerman" <jordan@jordanzimmerman.com>
wrote:

> It’s the same as in normal ZooKeeper. Provide a background callback
> handler. e.g.
>
> client.create().inBackground(handler).forPath(…)
>
>
> On Jul 20, 2016, at 1:50 PM, Sakthipriyan Vairamani <
> sakthiprofessional@gmail.com> wrote:
>
> The documentation is very limited (actually I couldn't find anything
> covering this topic). I want to know how the errors are handled in async
> operations.
>
> Let's say I want to get data from a node, which doesn't exist in the ZK,
> with inBackground(BackgroundCallback). Now, How will I know that the
> operation
> has failed? I used curatorClient.getUnhandledErrorListenable.addListener,
> curatorClient.getConnectionStateListenable.addListener,
> and curatorClient.getCuratorListenable.addListener None of them generated
> any events.
>
>
>

Mime
View raw message