[
https://issues.apache.org/jira/browse/NIFI-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17602459#comment-17602459
]
Mark Payne commented on NIFI-10454:
-----------------------------------
Thanks for attaching [~nurullahcaliskan] .
So looking at the thread dump, I can see that none of the tasks are running in
ExecuteScript.
They are all in InvokeScriptedProcessor and InvokeHTTP.
So why do you see the active threads for ExecuteScript? Well, on startup, it
runs through all components that need to be started and queue up a task to
perform initialization (call @OnScheduled methods and whatnot). At that point,
it increments the number of Active Threads. When you look at the screen, it
just hasn't had a chance yet to initialize those components. So perhaps "Active
Threads" is not a great term for exactly what this represents. It really
represents a combination of "active threads" and "pending tasks" - the
initialization of those components are pending tasks.
So whenever you increase the number of Timer-Driven threads available, those
additional threads are able to handle those pending tasks of initializing
components.
Alternatively, if you do not increase the number of timer-driven threads
available, they should eventually get initialized and everything should move
on. But depending on how busy your InvokeScriptedProcessor, InvokeHTTP, and
other processors are, that may take a while.
> flowfiles not progressing
> -------------------------
>
> Key: NIFI-10454
> URL: https://issues.apache.org/jira/browse/NIFI-10454
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Nurullah Çalışkan
> Priority: Major
> Attachments: image (6).png, thread-dump.txt
>
>
> When the script body part of the execute script processor is set as set empty
> string and added to the nifi UI from the registry, 1 thread is open. The more
> processors there are, the more threads open. Because these threads are not
> terminated, the processors cannot proceed to the next runtime. This prevents
> flowfiles from progressing.
> I found a solution for this myself, so I'll share it. I found each processor
> one by one and terminated it. Problem solved. Then my flowfiles started to
> progress.
> This is the problem: I've seen nifi-1.15.x , nifi-1.16.0 and nifi-1.17.0, but
> haven't tried the others. I am using openjdk java 11.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
