[
https://issues.apache.org/jira/browse/CURATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720390#comment-14720390
]
ASF GitHub Bot commented on CURATOR-253:
----------------------------------------
Github user Randgalt commented on a diff in the pull request:
https://github.com/apache/curator/pull/100#discussion_r38231138
--- Diff:
curator-recipes/src/main/java/org/apache/curator/framework/recipes/nodes/PersistentEphemeralNode.java
---
@@ -111,11 +112,26 @@ public void stateChanged(CuratorFramework client,
ConnectionState newState)
{
if ( newState == ConnectionState.RECONNECTED )
{
+ if ( debugReconnectLatch != null )
+ {
+ try
+ {
+ debugReconnectLatch.await();
+ }
+ catch ( InterruptedException e )
+ {
+ Thread.currentThread().interrupt();
+ e.printStackTrace();
+ }
+ }
createNode();
}
}
};
+ @VisibleForTesting
+ volatile CountDownLatch debugReconnectLatch = null;
--- End diff --
Can't predict what thread it will come from. In the current use case it
doesn't need to be, but who knows in the future.
> Use new injectSessionExpiration() in the test module
> ----------------------------------------------------
>
> Key: CURATOR-253
> URL: https://issues.apache.org/jira/browse/CURATOR-253
> Project: Apache Curator
> Issue Type: Sub-task
> Components: Tests
> Reporter: Jordan Zimmerman
> Assignee: Jordan Zimmerman
> Fix For: 3.0.0
>
>
> ZK 3.5.0 adds the Testable interface and the injectSessionExpiration()
> method. Curator's KillSession utils should use this instead of what's
> currently done.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
