[
https://issues.apache.org/jira/browse/NIFI-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261379#comment-16261379
]
Fredrik Sko edited comment on NIFI-4629 at 11/21/17 7:59 PM:
-------------------------------------------------------------
Some additional notes:
* After generating the errors, the log claims to roll back the session
* The flowfiles in the originating queue (between GenerateFlowFile and
ControlRate as per my attached template) stays in the queue.
* The UI shows the queue still containing the flowfiles, however "empty queue"
and "list queue" both claims the queue is empty.
* Stopping the processors and trying to delete the connection yields a "Queue
is not empty" error message, which is expected given the number of items
queued, but inconsistent with the statement above.
I also tried moving the connection containing the stall/dead/inaccessible
flowfiles to another destination, but they are not processed any further and
remains in a state where I'm unable to recover them.
was (Author: frsk):
Some additional notes:
* After generating the errors, the log claims to roll back the session
* The flowfiles in the originating queue (between GenerateFlowFile and
ControlRate as per my attached template) stays in the queue.
* The UI shows the queue still containing the flowfiles, however "empty queue"
and "list queue" both claims the queue is empty.
* Stopping the processors and trying to delete the connection yields a "Queue
is not empty" error message, which is expected given the number of items
queued, but inconsistent with the statement above.
I also tried moving the connection containing the stall/dead/inaccessible
flowfiles to another destination, but the are not processed any further and
remains in a state where I'm unable to recover them.
> Non-existing attribute in ControlRate configuration causes
> NullPointerException
> -------------------------------------------------------------------------------
>
> Key: NIFI-4629
> URL: https://issues.apache.org/jira/browse/NIFI-4629
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Core UI
> Affects Versions: 1.4.0
> Environment: Ubuntu LTS 16.04
> openjdk-8-jre
> Reporter: Fredrik Sko
> Priority: Critical
> Labels: ControlRate, NullPointerException, Processor
> Attachments: ControlRate-NP.xml
>
>
> When using the ControlRate processor, defining the "Grouping Attribute" with
> a missing/non-existing attribute name produces NullPointerException errors.
> Processor configuration:
> {quote}
> Rate Control Criteria: flowfile count
> Maximum rate: 10
> Rate Controlled Attributes: (No value set)
> Time Duration: 1 min
> Grouping Attribute: foobar
> {quote}
> ControlRate with the following configuration when sent a flowfile without the
> attribute {{foobar}} generates the following error:
> bq. ControlRate\[id=dff05b32-015f-1000-db55-5957a9298bab]
> ControlRate\[id=dff05b32-015f-1000-db55-5957a9298bab] failed to process due
> to java.lang.NullPointerException; rolling back session: null
> Additionally, the incoming flowfiles now ends up in some "dead" state where
> I'm unable to even empty the queue.
> A simple template for reproduction is attached.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
