[ https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820408#comment-13820408 ]
Evaristo commented on CURATOR-72: --------------------------------- The problem is not the initial LOST. What is suspicious for me is having having another LOST after CONNECTED and before SUSPENDED. Somehow the natural ordering of the events is broken > 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)