[ 
https://issues.apache.org/jira/browse/NIFI-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417405#comment-15417405
 ] 

ASF GitHub Bot commented on NIFI-2545:
--------------------------------------

GitHub user markap14 opened a pull request:

    https://github.com/apache/nifi/pull/836

    NIFI-2545: Ensure that when @OnUnscheduled and @OnStopped methods are…

    … called that the active thread count takes that thread into account

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/markap14/nifi NIFI-2545

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/836.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #836
    
----
commit d6417ef43db2e0697b35ff1c67722abcfccf66c2
Author: Mark Payne <[email protected]>
Date:   2016-08-11T15:18:50Z

    NIFI-2545: Ensure that when @OnUnscheduled and @OnStopped methods are 
called that the active thread count takes that thread into account

----


> Cannot tell a processor is "STOPPING", can edit, cannot restart it
> ------------------------------------------------------------------
>
>                 Key: NIFI-2545
>                 URL: https://issues.apache.org/jira/browse/NIFI-2545
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework, Core UI
>    Affects Versions: 1.0.0
>            Reporter: Joseph Witt
>            Assignee: Mark Payne
>             Fix For: 1.0.0
>
>
> Testing ListenSMTP processor.  It has some bad behavior whereby it will not 
> stop when told to.  But on the UI i cannot tell that at all.  So, i went to 
> edit the processor config which I was able to do.  Then went to start it and 
> I get
> {quote}
> 7667f0c7-0156-1000-8181-5b556f8544da cannot be started because it is not 
> stopped. Current state is STOPPING
> {quote}
> There should be a visual indicator of its status and we should not be able to 
> edit a processor which is not stopped.
> More details on that specific case here 
> https://issues.apache.org/jira/browse/NIFI-2519#
> But key is that a bad behaving processor can allow the user to do things they 
> should not be able to.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to