[ https://issues.apache.org/jira/browse/NIFI-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15517041#comment-15517041 ]
ASF subversion and git services commented on NIFI-2636: ------------------------------------------------------- Commit 5a3d00c7bb171b4ca35c5533f670ade9513ab6d3 in nifi's branch refs/heads/master from [~boardm26] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=5a3d00c ] NIFI-2636 resolve thread safety problem in UnpackContent Signed-off-by: Joe Skora <jsk...@apache.org> > 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.8.0 > > > 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)