[
https://issues.apache.org/jira/browse/NIFI-862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14703196#comment-14703196
]
Mark Payne commented on NIFI-862:
---------------------------------
[~aldrin]: Pushed changes to master. I created a new ticket, NIFI-869, to
address the odd logging issue that you are pointing out. I think it should
actually be addressed in the ComponentLog class
> If a Controller Service fails to start, a Processor depending on it will not
> stop
> ---------------------------------------------------------------------------------
>
> Key: NIFI-862
> URL: https://issues.apache.org/jira/browse/NIFI-862
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Critical
> Fix For: 0.3.0
>
> Attachments:
> 0001-NIFI-862-Ensure-that-if-we-are-unable-to-stop-a-cont.patch
>
>
> Steps to replicate:
> 1. Add a DBCPConnectionPool controller service
> 2. Configure it with an invalid driver class name
> 3. Enable the Controller Service
> 4. Add a processor that depends on DBCPConnectionPool (for example,
> ExecuteSQL) to the flow
> 5. Configure the processor to use the controller service that is now failing
> to start (because you gave it an invalid driver class name)
> 6. Start the Processor
> 7. Stop the Processor
> NiFi will hang, waiting for the service to properly start.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
