[
https://issues.apache.org/jira/browse/NIFI-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15719178#comment-15719178
]
Justin M Cavinee commented on NIFI-3144:
----------------------------------------
One other thing, which I haven't been able to consistently reproduce so I
haven't opened a separate ticket yet, but there seem be issues with trying to
do anything with the Exception Handling. On a couple of my scripts, I used to
have rescue => e, and then tried to put the exception message and backtrace
into different attributes. I've seen two unusual errors when I did this. One
was an exception claiming it couldn't convert between jruby Exception types
(which I expect is related to https://issues.apache.org/jira/browse/NIFI-2970,
with different exceptions being placed into the same variable 'e' causing
issues. Other times, I'm getting an exception saying invalid symbol, with a
diamond containing a question mark. This one is very inconsistent, sometimes
I'll start a script, have the error, restart the script, error goes away, but
it consistently does *not* happen if I don't try to store or access the
exception (=> e).
> 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)
