[
https://issues.apache.org/jira/browse/NIFI-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023322#comment-16023322
]
Mark Payne commented on NIFI-3671:
----------------------------------
Okay, so I was able to replicate this quite easily now, in a very slightly
different fashion than you described. I created the 3 GenerateFlowFile procs
like you mentioned and sent all to UpdateAttribute. I then start the 3
processors and then stop them. All works fine the first time. I then start
UpdateAttribute, which swaps the data back in and destroys it. Then when the
queues are empty, I stopped UpdateAttribute and started GenerateFlowFile again,
which causes the NPE. It is due to a bug in swapping the data in. Attached is a
PR that addresses it. Should be very easy to replicate & verify fix.
> GenerateFlowFile throws NPE in FileSystemRepository
> ---------------------------------------------------
>
> Key: NIFI-3671
> URL: https://issues.apache.org/jira/browse/NIFI-3671
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.2.0
> Environment: Ubuntu Linux 14.04.5 LTS, x86, NiFi 1.2.0-SNAPSHOT, Java
> 1.8.0_102
> Reporter: Joe Skora
> Assignee: Mark Payne
> Fix For: 1.3.0
>
> Attachments: flow.xml, genff-npe.log, priority.groovy
>
>
> While volume testing, {{GenerateFlowFile}} is randomly throwing
> {{NullPointerException}} during startup. The NPE occurs in
> {{FileSystemRepository.write()}} called from
> {{BufferedOutputStream.flushBuffer()}} and results in an Administrative Yield.
> When it happens, the bulletin shows up on the processors immediately after
> starting them. Starting them a second time will often succeed, but sometimes
> it takes a multiple retries. When the {{GenerateFlowFile}} processors are
> started for these tests, the graph is typically empty.
> Log entries for an example Thread are attached. This looks similar to
> [NIFI-2551|https://issues.apache.org/jira/browse/NIFI-2551], but that is
> marked as being fixed in 1.0.0.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
