[
https://issues.apache.org/jira/browse/NIFI-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Skora updated NIFI-3671:
----------------------------
Attachment: priority.groovy
flow.xml
Granted, it's not pretty, but this flow produced the NPE, though only after
many iterations. The 2nd row UpdateAttribute processors ("priority
[1|10|100]") and bottom LogAttribute were always stopped. The loop in the
middle was running (though without content) sometimes and stopped sometimes.
I don't think it's pertinent to the NPE problem, but the Groovy script checks
FlowFile priorities and forwards only high priority FlowFile if any are found
and otherwise forwards all FlowFiles.
> 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: 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)
