[
https://issues.apache.org/jira/browse/NIFI-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956895#comment-15956895
]
Mark Payne commented on NIFI-3671:
----------------------------------
[~jskora] - thanks for reporting this. I'm hoping that you can clarify a few
things for me.
You marked this as affecting 1.2.0 - does that mean that you're running the
latest master build? When you say "Starting them a second time will often
succeed" does that mean that you are actually stopping the processor and
starting it again? Or do you mean the next time that the processor is triggered
to run, after the administrative yield duration? You say "When the
GenerateFlowFile processors are started for these tests, the graph is typically
empty." but if you have a GenerateFlowFile processor on your graph then the
graph is not empty :) Can you clarify what you meant there?
Also, what kind of hardware are you running this on? A laptop/VM? Or a server?
SSD or spinning disk? What I guess I'm trying to get at here is - are you I/O
bound or CPU bound?
Thanks
> 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
> Priority: Critical
> Fix For: 1.2.0
>
> Attachments: genff-npe.log
>
>
> 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)
