[
https://issues.apache.org/jira/browse/NIFIREG-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16255876#comment-16255876
]
ASF GitHub Bot commented on NIFIREG-55:
---------------------------------------
GitHub user bbende opened a pull request:
https://github.com/apache/nifi-registry/pull/39
NIFIREG-55 Adding a startupFailure method to be called when exception…
…s are caught in JettyServer which will called system.exit
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bbende/nifi-registry NIFIREG-55
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi-registry/pull/39.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #39
----
commit 7edb70bccd93ce87256245099d54fc7495e45745
Author: Bryan Bende <[email protected]>
Date: 2017-11-16T19:57:23Z
NIFIREG-55 Adding a startupFailure method to be called when exceptions are
caught in JettyServer which will called system.exit
----
> Process does not exit when application fails to start correctly
> ---------------------------------------------------------------
>
> Key: NIFIREG-55
> URL: https://issues.apache.org/jira/browse/NIFIREG-55
> Project: NiFi Registry
> Issue Type: Bug
> Reporter: Bryan Bende
> Assignee: Bryan Bende
>
> The nifi-registry process appears to still be running even when the
> application didn't start up correctly. Some examples are setting an https web
> port without providing keystore/trustore properties, or providing an
> authorizer id that does not exist.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
