You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2017/04/05 01:27:41 UTC

[jira] [Commented] (NIFI-3671) GenerateFlowFile throws NPE in FileSystemRepository

    [ https://issues.apache.org/jira/browse/NIFI-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956162#comment-15956162 ] 

Joseph Witt commented on NIFI-3671:
-----------------------------------

Raising the priority of this and tagging it to be fixed in 1.2.0. This sort of thing in the filesystemrepo and in core framework code needs to be looked into for sure. 

[~jskora] thanks for reporting.  Can you share the details of your GenerateFlowFile configuration and the flow after that?

> 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)