[
https://issues.apache.org/jira/browse/NIFI-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992198#comment-14992198
]
Oleg Zhurakousky edited comment on NIFI-1099 at 11/5/15 6:35 PM:
-----------------------------------------------------------------
The patch may not address all of the components, but it does address the
Interrupt handling in NiFi core modules. IMHO we should continue to spot these
miss-handlings and fix them as part of addressing other issues.
Perhaps we should also publish some guide (check list) on the wiki for how to
address special cases such as this one, which is a source of a lot of confusion
in java in general.
was (Author: ozhurakousky):
The patch may not address all of the components, but it does address the
Interrupt handling in NiFi core modules. IMHO we should continue to spot these
miss-handlings and fix it as part of addressing other issues.
Perhaps we should also publish some guide (check list) on the wiki for how o
address special cases such as this one which is a source of a lot of confusion
in java in general.
> 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)
