[
https://issues.apache.org/jira/browse/CURATOR-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15815665#comment-15815665
]
ASF GitHub Bot commented on CURATOR-375:
----------------------------------------
Github user thecoop commented on a diff in the pull request:
https://github.com/apache/curator/pull/186#discussion_r95420664
--- Diff:
curator-recipes/src/test/java/org/apache/curator/framework/recipes/nodes/TestPersistentNode.java
---
@@ -136,4 +138,52 @@ public void testQuickCloseNodeExists() throws Exception
CloseableUtils.closeQuietly(client);
}
}
+
+ @Test
+ public void testInterruption() throws Exception
--- End diff --
This issue is a root cause of some significant problems we've encountered.
I'll have another look at this and come up with a more pertinent test case.
> Fix thread interruption being reported twice
> --------------------------------------------
>
> Key: CURATOR-375
> URL: https://issues.apache.org/jira/browse/CURATOR-375
> Project: Apache Curator
> Issue Type: Bug
> Affects Versions: 2.11.1
> Reporter: Simon Cooper
> Assignee: Jordan Zimmerman
>
> When a curator operation thread is interrupted, some classes
> ({{PersistentNode}} {{ConnectionState}} primarily) report the interruption in
> two ways at the same time - by re-marking the thread interruption status
> *and* throwing {{InterruptedException}} - this makes it look like the thread
> has been interrupted twice, rather than once.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
