curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-375) Fix thread interruption being reported twice
Date Tue, 10 Jan 2017 17:58:58 GMT

    [ https://issues.apache.org/jira/browse/CURATOR-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15815666#comment-15815666
] 

ASF GitHub Bot commented on CURATOR-375:
----------------------------------------

Github user thecoop closed the pull request at:

    https://github.com/apache/curator/pull/186


> 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)

Mime
View raw message