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

Matt Gilman commented on NIFI-694:
----------------------------------

Controller Services have no way of relaying errors that occur when enabling or 
disabling and Reporting Tasks cannot whiling being scheduled and unscheduled. 
We will use Bulletins to do this. These bulletins will need to be added for the 
component itself and for the system as well so that they can be rendered on the 
canvas. The component specific bulletins will need to be rendered in the 
service and task table as well as the dialog used for enabling and disabling 
controller services.

We will also update the dialog used to enable and disable controller services 
to better indicate their current state. When the user opts to cancel a request 
to enable or disable there should be no confusion regarding their current 
state. After canceling, the user will be able to close the dialog and see the 
updated states in the service and task table. From there they will be able to 
take further action as needed. 



> 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)

Reply via email to