Mark Payne created NIFI-8731:
--------------------------------

             Summary: When updating Parameter Context, sometimes see failure: 
processor cannot be started because it is not stopped. Current state is STOPPING
                 Key: NIFI-8731
                 URL: https://issues.apache.org/jira/browse/NIFI-8731
             Project: Apache NiFi
          Issue Type: Bug
            Reporter: Mark Payne
            Assignee: Mark Payne


To replicate:
 * Create a Process Group with a Parameter Context bound
 * Create a Processor that references a Parameter
 * Start the Processor
 * Change Parameter to a value that will make the processor invalid
 * Attempt to change the Parameter again

This will result in a stack trace similar to:
{code:java}
org.apache.nifi.web.util.LifecycleManagementException: Failed to transition 
components to a state of RUNNING due to Node localhost:8481 is unable to 
fulfill this request due to: 3528126f-017a-1000-0000-0000003d5574 cannot be 
started because it is not stopped. Current state is STOPPING
        at 
org.apache.nifi.web.util.ClusterReplicationComponentLifecycle.scheduleComponents(ClusterReplicationComponentLifecycle.java:128)
        at 
org.apache.nifi.web.api.ParameterContextResource.restartProcessors(ParameterContextResource.java:987)
        at 
org.apache.nifi.web.api.ParameterContextResource.updateParameterContext(ParameterContextResource.java:885)
        at 
org.apache.nifi.web.api.ParameterContextResource.lambda$submitUpdateRequest$17(ParameterContextResource.java:812)
        at 
org.apache.nifi.web.api.concurrent.AsyncRequestManager$2.run(AsyncRequestManager.java:117)
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        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:748) {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to