[jira] [Created] (CURATOR-122) ConnectionStateListener advertises READ_ONLY instead of CONNECTED the first time around

Benjamin Jaton created CURATOR-122: -- Summary: ConnectionStateListener advertises READ_ONLY instead of CONNECTED the first time around Key: CURATOR-122 URL: https://issues.apache.org/jira/browse/CURATOR-122

[jira] [Created] (CURATOR-123) ConnectionStateListener is confused by READ_ONLY state

Benjamin Jaton created CURATOR-123: -- Summary: ConnectionStateListener is confused by READ_ONLY state Key: CURATOR-123 URL: https://issues.apache.org/jira/browse/CURATOR-123 Project: Apache Curator

[jira] [Updated] (CURATOR-123) ConnectionStateListener is confused by READ_ONLY state

[ https://issues.apache.org/jira/browse/CURATOR-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Jaton updated CURATOR-123: --- Attachment: Test.java Sample code used to reproduce the bug ConnectionStateListener is

[jira] [Closed] (CURATOR-122) ConnectionStateListener advertises READ_ONLY instead of CONNECTED the first time around

[ https://issues.apache.org/jira/browse/CURATOR-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Jaton closed CURATOR-122. -- This is fixed in trunk. ConnectionStateListener advertises READ_ONLY instead of CONNECTED the

[jira] [Updated] (CURATOR-125) ConnectionStateListener is confused by READ_ONLY state

[ https://issues.apache.org/jira/browse/CURATOR-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Jaton updated CURATOR-125: --- Attachment: Test.java ConnectionStateListener is confused by READ_ONLY state

[jira] [Commented] (CURATOR-125) ConnectionStateListener is confused by READ_ONLY state

[ https://issues.apache.org/jira/browse/CURATOR-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075259#comment-14075259 ] Benjamin Jaton commented on CURATOR-125: I recreated everything from the trunk

[jira] [Created] (CURATOR-134) Curator sends a connection LOST event before sessionTimeout

Benjamin Jaton created CURATOR-134: -- Summary: Curator sends a connection LOST event before sessionTimeout Key: CURATOR-134 URL: https://issues.apache.org/jira/browse/CURATOR-134 Project: Apache

[jira] [Updated] (CURATOR-134) Curator sends a connection LOST event before sessionTimeout

[ https://issues.apache.org/jira/browse/CURATOR-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Jaton updated CURATOR-134: --- Attachment: Test.java Curator sends a connection LOST event before sessionTimeout

[jira] [Commented] (CURATOR-134) Curator sends a connection LOST event before sessionTimeout

[ https://issues.apache.org/jira/browse/CURATOR-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14082996#comment-14082996 ] Benjamin Jaton commented on CURATOR-134: Note that there is no need to use a

[jira] [Commented] (CURATOR-134) Curator sends a connection LOST event before sessionTimeout

[ https://issues.apache.org/jira/browse/CURATOR-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14094292#comment-14094292 ] Benjamin Jaton commented on CURATOR-134: Regardless of the sessionTimeout, with a

[jira] [Commented] (CURATOR-134) Curator sends a connection LOST event before sessionTimeout

[ https://issues.apache.org/jira/browse/CURATOR-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14279337#comment-14279337 ] Benjamin Jaton commented on CURATOR-134: Yes and I'am concerned about Scott

[jira] [Commented] (CURATOR-134) Curator sends a connection LOST event before sessionTimeout

[ https://issues.apache.org/jira/browse/CURATOR-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14279361#comment-14279361 ] Benjamin Jaton commented on CURATOR-134: I agree that there seems to be something

[jira] [Created] (CURATOR-185) Create a LOST_SESSION connection state

Benjamin Jaton created CURATOR-185: -- Summary: Create a LOST_SESSION connection state Key: CURATOR-185 URL: https://issues.apache.org/jira/browse/CURATOR-185 Project: Apache Curator Issue

[jira] [Updated] (CURATOR-268) Curator client doesn't behave well when it loses connection: CRUD operation fail

[ https://issues.apache.org/jira/browse/CURATOR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Jaton updated CURATOR-268: --- Attachment: TestCuratorSaveConnLoss.java The Test > Curator client doesn't behave well when

[jira] [Created] (CURATOR-268) Curator client doesn't behave well when it loses connection: CRUD operation fail

Benjamin Jaton created CURATOR-268: -- Summary: Curator client doesn't behave well when it loses connection: CRUD operation fail Key: CURATOR-268 URL: https://issues.apache.org/jira/browse/CURATOR-268

[jira] [Reopened] (CURATOR-268) Curator client doesn't behave well when it loses connection: CRUD operation fail

[ https://issues.apache.org/jira/browse/CURATOR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Jaton reopened CURATOR-268: >From the ZK developers: "The behavior is expected. If your client loses its connection, then

[jira] [Commented] (CURATOR-268) Curator client doesn't behave well when it loses connection: CRUD operation fail

[ https://issues.apache.org/jira/browse/CURATOR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14941785#comment-14941785 ] Benjamin Jaton commented on CURATOR-268: Yeah they would be very useful I think. What I do as a

[jira] [Created] (CURATOR-309) ConnectionState:244 - Authentication failed

Benjamin Jaton created CURATOR-309: -- Summary: ConnectionState:244 - Authentication failed Key: CURATOR-309 URL: https://issues.apache.org/jira/browse/CURATOR-309 Project: Apache Curator

[jira] [Updated] (CURATOR-355) Curator client fails when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Jaton updated CURATOR-355: --- Summary: Curator client fails when connecting to read-only ensemble (was: Curator client

[jira] [Commented] (CURATOR-355) Curator client fails when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15563014#comment-15563014 ] Benjamin Jaton commented on CURATOR-355: Sounds good, I will check the 3.x release. But I won't

[jira] [Created] (CURATOR-355) Curator client hangs when connecting to read-only ensemble

Benjamin Jaton created CURATOR-355: -- Summary: Curator client hangs when connecting to read-only ensemble Key: CURATOR-355 URL: https://issues.apache.org/jira/browse/CURATOR-355 Project: Apache

[jira] [Updated] (CURATOR-355) Curator client hangs when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Jaton updated CURATOR-355: --- Attachment: test2.log > Curator client hangs when connecting to read-only ensemble >

[jira] [Commented] (CURATOR-355) Curator client fails when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15562967#comment-15562967 ] Benjamin Jaton commented on CURATOR-355: I used Curator 2.11.0. > Curator client fails when

[jira] [Commented] (CURATOR-355) Curator client fails when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15563495#comment-15563495 ] Benjamin Jaton commented on CURATOR-355: Does it need a backport? Just a fix of the existing

[jira] [Commented] (CURATOR-355) Curator client fails when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15563532#comment-15563532 ] Benjamin Jaton commented on CURATOR-355: Just to clarify, in this case there is still 1 of the ZK

[jira] [Updated] (CURATOR-359) Curator can't connect to Read Only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Jaton updated CURATOR-359: --- Affects Version/s: 3.2.1 > Curator can't connect to Read Only ensemble >

[jira] [Updated] (CURATOR-359) Curator can't connect to Read Only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Jaton updated CURATOR-359: --- Attachment: TestCuratorRetry.java output.txt code+output > Curator can't

[jira] [Updated] (CURATOR-355) Curator client fails when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Jaton updated CURATOR-355: --- Description: ZK is 3.5.1-alpha I have a 3 nodes ZK cluster , readonly mode is

[jira] [Commented] (CURATOR-355) Curator client fails when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15566676#comment-15566676 ] Benjamin Jaton commented on CURATOR-355: Let's note that the code you provided using the

[jira] [Commented] (CURATOR-355) Curator client fails when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15565929#comment-15565929 ] Benjamin Jaton commented on CURATOR-355: Is there a documentation somewhere that talks about what

[jira] [Commented] (CURATOR-355) Curator client fails when connecting to read-only ensemble

[ https://issues.apache.org/jira/browse/CURATOR-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15563713#comment-15563713 ] Benjamin Jaton commented on CURATOR-355: So when I connect using ZK API directly with