nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joseph Witt (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-1099) Interrupted status is not restored
Date Fri, 06 Nov 2015 00:55:27 GMT

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

Joseph Witt commented on NIFI-1099:
-----------------------------------

Oleg I think we need to make sure the interrupt status is reset by the executor.  And sweep
to ensure we had no goofy caller code.  As I wrote I believe I agree it is always safe but
let's be sure we understand the executor behavior.  I would not want the fact that a thread
was ever interrupted to linger.

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

Mime
View raw message