[
https://issues.apache.org/jira/browse/NIFI-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14591706#comment-14591706
]
Matt Gilman commented on NIFI-694:
----------------------------------
[~markap14] In this specific case you outlined, why is the service considered
valid? It seems that there may be some validation missing.
That said, we should still be handling this case. Let's talk about the
mechanism for relaying the necessary information back to the user. During
OnEnabled, there doesn't appear to be any way for a controller service to
indicate that it's having problems whether they are misconfigurations or some
sort of environmental issue. It appears that it can only throw an
InitializationException. Not entirely sure of the correct answer here. Should
the framework stop trying to enable the service after X attempts and return a
failure to the client?
> 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)
