[
https://issues.apache.org/jira/browse/NIFI-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14591748#comment-14591748
]
Mark Payne commented on NIFI-694:
---------------------------------
Matt,
Yes, I think the framework needs to keep retrying. We do the same thing for
processors: if their @OnScheduled method throws an Exception we keep trying.
For controller services, it's more important. If there's something
environmental that will be fixed (for instance a flow is brought up on a new
node and it needs some external file that will be pulled by GetHTTP), then we
still need to schedule the service to run. Otherwise, any processor depending
on it won't start.
> If Enabling Controller Service fails, no indication is provided to user
> -----------------------------------------------------------------------
>
> Key: NIFI-694
> URL: https://issues.apache.org/jira/browse/NIFI-694
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework, Core UI
> Reporter: Mark Payne
> Fix For: 0.3.0
>
>
> To replicate the issue:
> 1. Add a DBCPService controller service.
> 2. Configure service. For the Driver Url use "file://tmp/non-existent-file"
> or use an invalid Driver Class Name.
> 3. Click Apply.
> 4. Click Enable.
> The UI will show the spinner indefinitely, as the service will keep failing
> to enable because it throws Exceptions from its @OnEnabled method. The UI
> should provide some sort of indication that this is occurring. Otherwise, it
> appears to the user that the system is non-responsive.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
