[
https://issues.apache.org/jira/browse/NIFI-10772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17655509#comment-17655509
]
Nissim Shiman commented on NIFI-10772:
--------------------------------------
Here is the stack trace (also uncaught/unattributable) on nifi shutdown when a
processor relies on a controller service in the state mention above
{code:java}
2023-01-06 15:46:40,492 ERROR [Monitor Processor Lifecycle Thread-2]
org.apache.nifi.engine.FlowEngine Uncaught Exception in Runnable task
java.util.concurrent.RejectedExecutionException: Task
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@398f32ee
rejected from org.apache.nifi.engine.FlowEngine@a814d7d[Shutting down, pool
size = 10, active threads = 0, queued tasks = 3, completed tasks = 257823]
at
java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063)
at
java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
at
java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:326)
at
java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:549)
at org.apache.nifi.engine.FlowEngine.schedule(FlowEngine.java:102)
at
java.util.concurrent.ScheduledThreadPoolExecutor.submit(ScheduledThreadPoolExecutor.java:648)
at
org.apache.nifi.controller.scheduling.StandardProcessScheduler$4.scheduleTask(StandardProcessScheduler.java:350)
at
org.apache.nifi.controller.StandardProcessorNode.initiateStart(StandardProcessorNode.java:1803)
at
org.apache.nifi.controller.StandardProcessorNode.lambda$null$6(StandardProcessorNode.java:1715)
at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)
{code}
To see this, do the following steps (similar to those in ticket description
above):
Enable StandardRestrictedSSLContextService
Create ListenHTTP processor
set processor's SSL Context Service to use StandardRestrictedSSLContextService
just enabled
Start ListenHTTP
Shutdown nifi
remove keystore StandardRestrictedSSLContextService relied on (or move it to
different location on filesystem)
start nifi
stop nifi
Two errors will be seen, one for the controller service and one for the
processor.
> Unattributable error on nifi shutdown when controller service was unable to
> be started
> --------------------------------------------------------------------------------------
>
> Key: NIFI-10772
> URL: https://issues.apache.org/jira/browse/NIFI-10772
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.18.0, 1.20.0
> Reporter: Nissim Shiman
> Assignee: Nissim Shiman
> Priority: Major
>
> This error occurs when nifi is unable to start a controller service that is
> supposed to be in an enabled state. On shutdown, nifi will give an error
> (stacktrace below)
> To reproduce, for example using, StandardRestrictedSSLContextService:
> Enable StandardRestrictedSSLContextService
> Shutdown nifi
> remove keystore StandardRestrictedSSLContextService relied on (or move it to
> different location on filesystem)
> start nifi
> stop nifi
> When nifi is shutdown the following uncaught/non-attributable error is in
> nifi-app.log:
> {code:java}
> 2023-01-06 15:46:41,085 ERROR [Timer-Driven Process Thread-5]
> org.apache.nifi.engine.FlowEngine Uncaught Exception in Runnable task
> java.util.concurrent.RejectedExecutionException: Task
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@2867c735
> rejected from org.apache.nifi.e
> ngine.FlowEngine@a814d7d[Shutting down, pool size = 10, active threads = 3,
> queued tasks = 0, completed tasks = 257823]
> at
> java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063)
> at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:326)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:533)
> at org.apache.nifi.engine.FlowEngine.schedule(FlowEngine.java:87)
> at
> org.apache.nifi.controller.service.StandardControllerServiceNode$2.run(StandardControllerServiceNode.java:591)
> at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:750)
> {code}
> It is unclear from the current log output as to what the underlying cause of
> it was (i.e. which controller service StandardControllerServiceNode is having
> trouble with)
> A similar non-attributable error is also seen on nifi shutdown for a
> processor that relies on this controller service.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
