You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matt Burgess (Jira)" <ji...@apache.org> on 2021/06/02 13:48:00 UTC
[jira] [Commented] (NIFI-8625) ExecuteScript processor always stuck
after restart or multi thread
[ https://issues.apache.org/jira/browse/NIFI-8625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355739#comment-17355739 ]
Matt Burgess commented on NIFI-8625:
------------------------------------
The script configurators have become cumbersome, they were originally designed just to add whatever imports were needed and to find libraries/modules from the module paths such as JARs and Jython modules. The compilation stuff has made them unnecessarily complex and awkward, I think we should move only the relevant code into a ScriptRunner interface and impls and the scripted components just need to set up a runner (passing in the appropriate ScriptEngine) for each task, then set the bindings when evaluating the script. Will post a PR shortly for review
> ExecuteScript processor always stuck after restart or multi thread
> ------------------------------------------------------------------
>
> Key: NIFI-8625
> URL: https://issues.apache.org/jira/browse/NIFI-8625
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.13.2
> Reporter: KevinSky
> Assignee: Matt Burgess
> Priority: Critical
> Attachments: executeScript_nifi_8625.xml, image-2021-05-21-16-22-34-775.png
>
>
> In single thread, executeScript just stop and start, flow file always stuck in connections.
> In multi thread.executeScript always throw exception like is already marked for transfer in or is not known in this session.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)