[
https://issues.apache.org/jira/browse/NIFI-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15433570#comment-15433570
]
ASF GitHub Bot commented on NIFI-2636:
--------------------------------------
GitHub user mosermw opened a pull request:
https://github.com/apache/nifi/pull/923
NIFI-2636 resolve thread safety problem in UnpackContent
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mosermw/nifi NIFI-2636
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/923.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #923
----
commit 83bd31552852aad23402449c05f0ebf3a9b6acfc
Author: Mike Moser <[email protected]>
Date: 2016-08-23T20:41:13Z
NIFI-2636 resolve thread safety problem in UnpackContent
----
> 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: 0.7.0
> Reporter: Michael Moser
> Assignee: Michael Moser
>
> 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)
