[
https://issues.apache.org/jira/browse/NIFI-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679182#comment-14679182
]
Aldrin Piri commented on NIFI-831:
----------------------------------
Please correct me if I'm wrong, but to clarify, the issue in this case was that
the processor was initialized but never scheduled, and then additional changes
were made triggering the NPE due to the message queue never being instantiated?
Patch looks good to remedy that problem, +1.
> GetTwitter can throw NullPointerException if modifying properties without
> scheduling to run first
> -------------------------------------------------------------------------------------------------
>
> Key: NIFI-831
> URL: https://issues.apache.org/jira/browse/NIFI-831
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Critical
> Fix For: 0.3.0
>
> Attachments:
> 0001-NIFI-831-NIFI-799-Fixed-a-NullPointerException-use-a.patch
>
>
> We've seen a NPE get thrown when modifying properties for the GetTwitter
> Processor:
> 2015-08-08 14:02:57,299 ERROR [NiFi Web Server-18]
> o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred:
> java.lang.NullPointerException. Returning Internal Server Error response.
> java.lang.NullPointerException: null
> at
> org.apache.nifi.processors.twitter.GetTwitter.onPropertyModified(GetTwitter.java:204)
> ~[na:na]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
