[
https://issues.apache.org/jira/browse/NIFI-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14613317#comment-14613317
]
Mark Payne commented on NIFI-745:
---------------------------------
[~mcgilman] I think it's really a bit of a gray area. However, the consequences
of how it works now are pretty terrible. And it's unlikely that someone really
wants the behavior of being called repeatedly in the event that the services
throws the exception. The invoking of the method is run in a background thread,
so if someone does need that behavior, they could certainly implement the
method to catch the Exception, sleep for a bit, and retry. So I would vote that
we go ahead and change it.
> Disabling Controller Service stuck
> ----------------------------------
>
> Key: NIFI-745
> URL: https://issues.apache.org/jira/browse/NIFI-745
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Matt Gilman
> Fix For: 0.2.0
>
>
> Per the nifi-api a controller service OnDisable method will be invoked when
> the user disables that service. If that method fails with an exception it
> will be retried a short time later. This will continue until it successfully
> completes.
> Unfortunately, this means that if services continually throws an exception
> during OnDisable the user will not be able to do anything with the service.
> This is because controller services need to be Disabled in order to support
> editing its configuration or attempting to Enable. The service in question
> will not transition to the Disabled state until its OnDisable completes
> without issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
