[
https://issues.apache.org/jira/browse/NIFI-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Percivall resolved NIFI-3144.
------------------------------------
Resolution: Not A Bug
This is not a bug in NiFi but is due to the default configuration of JRuby that
is used by the ScriptingProcessors as explained in NIFI-3406. When multiple
different ExecuteScript processors are running, the process session and
flowfile that each are using will continually be updating to the latest while
processing. So a processor could attempt to modify a flowfile that is not in
it's queue to begin with and even "forget" about flowfiles that it had already
grabbed.
In order to provide a better ExecuteScript UX (and avoid this issue) more
configuration for the different Script Engines should be exposed.
> Execute Script Invalid FlowFile in Queue
> ----------------------------------------
>
> Key: NIFI-3144
> URL: https://issues.apache.org/jira/browse/NIFI-3144
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Justin M Cavinee
> Attachments: EmptyQueue.png, ErrorMessage.png
>
>
> There seems to be some kind of error in clearing flow files from the source
> queue of the ExecuteScript Processor. I keep running into lingering
> flow-files in the queue that cannot be cleared, and don't show up in the list
> source queue (says no FlowFiles Present), but it continues to sit in the
> queue, and seems to cause the processor throw "Failed to Process Session"
> Exceptions as it start loading other that come through the processor.
> Will attach Screenshots of a queue with a flow file count but that says no
> files in queue and one of the error message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
