[
https://issues.apache.org/jira/browse/NIFI-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14591728#comment-14591728
]
Matt Gilman commented on NIFI-694:
----------------------------------
What is the context of that bulletin? I'm guessing that it's a
system/controller level bulletin. Not sure how this would get associated with a
particular controller service. Are you recommending that the framework should
continue to attempt to enable the service? Thinking about it more, I'm not sure
it should even retry once.
FWIW, the cancel button does work but doesn't provide immediate feedback to the
user. I've created a separate ticket to address this issue [1]
[1] https://issues.apache.org/jira/browse/NIFI-695
> 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)
