[
https://issues.apache.org/jira/browse/NIFI-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710103#comment-14710103
]
Mark Payne edited comment on NIFI-842 at 8/24/15 9:35 PM:
----------------------------------------------------------
Looks good on Windows. Created a flow that contained an AWS processor. Killed
NiFi with Task Manager, and the bootstrap restarted it. Then shutdown, removed
the AWS NAR and started NiFi. It failed to start, and the bootstrap reported
this in the logs and shutdown. +1
was (Author: markap14):
Looks good on Windows. Created a flow that contained an AWS processor. Killed
NiFi with Task Manager, and the bootstrap restarted it. Then shutdown, removed
the AWS NAR and started NiFi. It failed to start, and the bootstrap reported
this in the logs and shutdown.
> If Bootstrap is unable to start NiFi, the process just stays around,
> listening for connections
> ----------------------------------------------------------------------------------------------
>
> Key: NIFI-842
> URL: https://issues.apache.org/jira/browse/NIFI-842
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Bryan Bende
> Fix For: 0.3.0
>
> Attachments: NIFI-842-2.patch, NIFI-842.patch
>
>
> When the bootstrap launches NiFi, it should allow some amount of time
> (perhaps a minute?) waiting to hear from NiFi. If it never hears, then it
> should assume that the app was unable to start at all. In this case,
> attempting to start it again is not going to be very helpful, so the
> bootstrap should just exit
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
