You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Michael Moser (JIRA)" <ji...@apache.org> on 2016/10/07 18:58:20 UTC

[jira] [Updated] (NIFI-2636) UnpackContent has concurrent thread safety issue, causes flowfiles to fail

     [ https://issues.apache.org/jira/browse/NIFI-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Moser updated NIFI-2636:
--------------------------------
    Fix Version/s:     (was: 0.8.0)
                   0.7.1

> UnpackContent has concurrent thread safety issue, causes flowfiles to fail
> --------------------------------------------------------------------------
>
>                 Key: NIFI-2636
>                 URL: https://issues.apache.org/jira/browse/NIFI-2636
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.0.0, 0.7.0
>            Reporter: Michael Moser
>            Assignee: Michael Moser
>             Fix For: 1.1.0, 0.7.1
>
>
> Shortly after merging NIFI-2611 I took a last look at the code and noticed that each onTrigger() call, when the Packaging Format property is set to "use mime.type attribute", that the class instance variable "private Unpacker unpacker" can change.  When UnpackContent is set to > 1 concurrent task, this isn't thread safe.  Thread A can set the unpacker to the TarUnpacker, but before it gets a chance to unpack its tar file, Thread B changes the unpacker to a FlowFileUnpackagerV3 which causes Thread A to fail its unpack.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)