[
https://issues.apache.org/jira/browse/NIFI-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421662#comment-15421662
]
ASF subversion and git services commented on NIFI-2551:
-------------------------------------------------------
Commit 25f816d32ab466d2ac1ad96cdb95e7359d085884 in nifi's branch refs/heads/0.x
from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=25f816d ]
NIFI-2551: Addressed a threading issue in the StandardResourceClaimManager and
performed some refactoring so that we can ensure thread-safety across different
components of the application, such as ProcessSession and WriteAheadFlowFile
Repository when interacting with the StandardResourceClaimManager. Update
DebugFlow to allow it to write to a FlowFile multiple times, which exposes the
concurrency bug. Also avoided calling ContentRepository.remove() from
ProcessSession whenever the content is no longer needed, as that can cause
problems now that the Resource Claim is backing the content claim.
> Rare condition causes FileSystemRepository NPE
> ----------------------------------------------
>
> Key: NIFI-2551
> URL: https://issues.apache.org/jira/browse/NIFI-2551
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.0.0, 0.7.0
> Reporter: Michael Moser
> Assignee: Mark Payne
> Priority: Blocker
> Fix For: 1.0.0, 0.8.0
>
>
> In rare unpredictable cases when NiFi is processing a heavy load, we see
> FileSystemRepository throw a NullPointerException
> {noformat}
> java.lang.NullPointerException
> at o.a.n.c.r.FileSystemRepository$2.write(FileSystemRepository.java:918)
> [nifi-framework-core-0.7.0.jar]
> at
> o.a.n.c.r.io.DisableOnCloseOutputStream.write(DisableOnCloseOutputStream.java:49)
> ....
> Suppressed: java.lang.NullPointerException
> at
> o.a.n.c.r.FileSystemRepository$2.flush(FileSystemRepository.java:934)
> [nifi-framework-core-0.7.0.jar]
> at
> o.a.n.c.r.io.DisableOnCloseOutputStream.close(DisableOnCloseOutputStream.java:68)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)