curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Evaristo José Camarero <>
Subject Re: [jira] [Commented] (CURATOR-72) Background operations don't wait for connection timeout
Date Mon, 18 Nov 2013 09:39:19 GMT
Hi there,

I am using the regression of my own app and now I do not see the unexpected LOST events anymore,
but I see some cases in which the LOST event is not fired.

I have a CuratorFramework client with several recipes (leader election, caches) and I close
the ZK servers, and I am not getting the LOST event  (Session TO is set to 15 secs). The
test is waiting even 60 secs to wait for the LOST event, but the event is not fired.



El Domingo 17 de noviembre de 2013 21:49, Jordan Zimmerman (JIRA) <>


Jordan Zimmerman commented on CURATOR-72:

[], can you test branch "CURATOR-72"? I've worked on state
changes in the background so that they match foreground operations. Please let me know.

> Background operations don't wait for connection timeout
> -------------------------------------------------------
>                 Key: CURATOR-72
>                 URL:
>             Project: Apache Curator
>          Issue Type: Bug
         Components: Framework
>    Affects Versions: 2.3.0
>            Reporter: Evaristo Camarero
>            Assignee: Jordan Zimmerman
>             Fix For: 2.3.1
>         Attachments:,,
> Background operations don't wait for the configured connection timeout before failing.
Attached test shows the problem.

This message was sent by Atlassian JIRA
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message