[
https://issues.apache.org/jira/browse/NIFI-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16222001#comment-16222001
]
Pierre Villard commented on NIFI-4537:
--------------------------------------
Hi,
Stopping a processor won't kill the running threads. If a thread cannot be
stopped, the processor will keep running until the thread finishes. The number
of running threads on your processor is shown on your screenshot (2). It means
that's something is running and cannot be stopped. I'd double check what
command you're executing with ExecuteStreamCommand and if the script is not the
issue, then take a thread dump of NiFi to check where threads are blocked
(bin/nifi.sh dump <file>) and attach the result to this JIRA.
Immediate solution to your problem is restarting NiFi.
> ExecuteStreamCommand stuck, cannot play cannot run
> --------------------------------------------------
>
> Key: NIFI-4537
> URL: https://issues.apache.org/jira/browse/NIFI-4537
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.3.0
> Reporter: dav
> Attachments: executeStreamCommand.png
>
>
> At a certain time the ExecuteStreamCommand get stucked, but it seems to be in
> running state.
> When I stop the proccessor from the web UI the processor seems to be stopped
> but If I try to Put in RUNNING state the stucked processor, with Nifi API
> REST, i get this response:
> 2017-10-27 08:50:43,749 INFO [NiFi Web Server-96840]
> o.a.n.w.a.c.IllegalStateExceptionMapper java.lang.IllegalStateException:
> 015e1005-8820-176e-f509-ca592def60b0 cannot be started because it is not
> stopped. Current state is STOPPING. Returning Conflict response.
> I found a hortonworks question already open but no solution is given
> [https://community.hortonworks.com/questions/131434/scheduling-executestreamcommand-processor-with-gen.html?childToView=142637#answer-142637]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
