[
https://issues.apache.org/jira/browse/NIFI-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992813#comment-14992813
]
ASF GitHub Bot commented on NIFI-1099:
--------------------------------------
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/115#issuecomment-154248804
Great book, great guy and if you can't get a book here is his writeup on
the subject - http://www.ibm.com/developerworks/library/j-jtp05236/.
The bottom line is blanket call to _Thread.interrupt()_ IMHO is always
safe. All it does is resets the interrupt flag that the caller _may_ choose to
ignore. NOT doing it simply implies withholding of the information that may or
may not be relevant.
> Interrupted status is not restored
> ----------------------------------
>
> Key: NIFI-1099
> URL: https://issues.apache.org/jira/browse/NIFI-1099
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Oleg Zhurakousky
> Assignee: Oleg Zhurakousky
> Fix For: 0.4.0
>
>
> There are few places with code that looks like this
> {code}
> try {
> Thread.sleep(val);
> } catch (InterruptedException ie) {
> }
> {code}
> . . . and the interrupted status of the thread is not restored. Need at the
> very least
> {code}
> Thread.currentThread().interrupt();
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
