[
https://issues.apache.org/jira/browse/NIFI-8461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17346518#comment-17346518
]
KevinSky commented on NIFI-8461:
--------------------------------
I found something new. If you set executeScript processor concurrent task more
than 1,It always throw exception like
{code:java}
//
2021-05-14 14:41:43,744 ERROR [Timer-Driven Process Thread-4]
o.a.nifi.processors.script.ExecuteScript
ExecuteScript[id=54bd3fab-5ce8-36c0-7d4d-25c69412379a]
ExecuteScript[id=54bd3fab-5ce8-36c0-7d4d-25c69412379a] failed to process due to
org.apache.nifi.processor.exception.ProcessException:
javax.script.ScriptException:
org.apache.nifi.processor.exception.FlowFileHandlingException:
org.apache.nifi.processor.exception.FlowFileHandlingException:
StandardFlowFileRecord[uuid=6d0c748f-d84c-49c1-ba16-ecb27550482a,claim=StandardContentClaim
[resourceClaim=StandardResourceClaim[id=1620958386186-1, container=default,
section=1], offset=33881,
length=1993],offset=0,name=B5_ALL_CELL_22.csv,size=1993] is not known in this
session (StandardProcessSession[id=16207]) in <script> at line number 14;
rolling back session: org.apache.nifi.processor.exception.ProcessException:
javax.script.ScriptException:
org.apache.nifi.processor.exception.FlowFileHandlingException:
org.apache.nifi.processor.exception.FlowFileHandlingException:
StandardFlowFileRecord[uuid=6d0c748f-d84c-49c1-ba16-ecb27550482a,claim=StandardContentClaim
[resourceClaim=StandardResourceClaim[id=1620958386186-1, container=default,
section=1], offset=33881,
length=1993],offset=0,name=B5_ALL_CELL_22.csv,size=1993] is not known in this
session (StandardProcessSession[id=16207]) in <script> at line number 14
{code}
or
{code:java}
//
2021-05-14 14:41:43,744 ERROR [Timer-Driven Process Thread-3]
o.a.nifi.processors.script.ExecuteScript
ExecuteScript[id=54bd3fab-5ce8-36c0-7d4d-25c69412379a] Failed to process
session due to org.apache.nifi.processor.exception.ProcessException:
javax.script.ScriptException:
org.apache.nifi.processor.exception.FlowFileHandlingException:
org.apache.nifi.processor.exception.FlowFileHandlingException:
StandardFlowFileRecord[uuid=6d0c748f-d84c-49c1-ba16-ecb27550482a,claim=StandardContentClaim
[resourceClaim=StandardResourceClaim[id=1620958386186-1, container=default,
section=1], offset=33881,
length=1993],offset=0,name=B5_ALL_CELL_22.csv,size=1993] is already marked for
transfer in <script> at line number 14:
org.apache.nifi.processor.exception.ProcessException:
javax.script.ScriptException:
org.apache.nifi.processor.exception.FlowFileHandlingException:
org.apache.nifi.processor.exception.FlowFileHandlingException:
StandardFlowFileRecord[uuid=6d0c748f-d84c-49c1-ba16-ecb27550482a,claim=StandardContentClaim
[resourceClaim=StandardResourceClaim[id=1620958386186-1, container=default,
section=1], offset=33881,
length=1993],offset=0,name=B5_ALL_CELL_22.csv,size=1993] is already marked for
transfer in <script> at line number 14
{code}
but It works right in 1.12.1
> Queue reports items but cannot list them
> ----------------------------------------
>
> Key: NIFI-8461
> URL: https://issues.apache.org/jira/browse/NIFI-8461
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.13.2
> Environment: Docker image apache/nifi :1.13.2, Windows 10 Pro, WSL 2
> (Ubuntu), x86_64
> Reporter: Kevin Aagaard
> Assignee: Matt Burgess
> Priority: Major
> Labels: queue
> Attachments: ExecuteScript_Queue_Issue.txt, NIFI-8461.zip,
> image-2021-04-22-08-48-58-117.png, image-2021-04-22-08-49-40-904.png,
> image-2021-04-27-14-23-07-849.png, image-2021-04-27-14-23-24-477.png
>
>
> The following segment of workflow demonstrates the issue. The queue reports
> that there are items within it, but they cannot be listed, even after
> stopping the consumer (and producer). Since this is in a Docker Container, it
> is unlikely an OS error.
>
> !image-2021-04-22-08-48-58-117.png!
>
> !image-2021-04-22-08-49-40-904.png!
> I do not currently have a simplified example workflow to recreate the error,
> but can work on it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
