Please post the test that shows this. I tested with the two tests you've posted already.
-JZ On Nov 18, 2013, at 1:39 AM, Evaristo José Camarero <[email protected]> wrote: > 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. > > Regards, > > Evaristo > > > > El Domingo 17 de noviembre de 2013 21:49, Jordan Zimmerman (JIRA) > <[email protected]> escribió: > > > [ > https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13824950#comment-13824950 > ] > > Jordan Zimmerman commented on CURATOR-72: > ----------------------------------------- > > [[email protected]], 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: https://issues.apache.org/jira/browse/CURATOR-72 >> 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: TestListener.java, TestListenerConnectedAtStart.java, >> test.java >> >> >> Background operations don't wait for the configured connection timeout >> before failing. Attached test shows the problem. > > > > -- > This message was sent by Atlassian JIRA > (v6.1#6144)
