[
https://issues.apache.org/jira/browse/NIFI-8625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17349072#comment-17349072
]
KevinSky commented on NIFI-8625:
--------------------------------
NIFI-8080caused this, in sigle thread,if it is not first in,compiledScriptRef
save the first time compiled value,and when executeScript restart, it only
clear
ScriptingComponentHelper.engineQ,but scriptEngineConfiguratorMap also has the
reference of compiledScriptRef. so that is why we see stuck in connections.
in multi thread, compiledScriptRef only save first engine compiled
CompiledScript. eval() method don't use the true engine to eval,so it always
throw exception
NIFI-8461 reveals this problem, but the scene description is incomplete.
> 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
> Priority: Critical
> Labels: ExecuteScript,stcuk
>
> In single thread, executeScript just stop and start, flow file always stuck
> in connections.
> In multi thread.executeScript always throw excetion 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)
