[
https://issues.apache.org/jira/browse/NIFI-13566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess updated NIFI-13566:
--------------------------------
Fix Version/s: 1.28.0
2.0.0-M5
Resolution: Fixed
Status: Resolved (was: Patch Available)
> JettyServer remains started when a ClassNotFoundError happens
> -------------------------------------------------------------
>
> Key: NIFI-13566
> URL: https://issues.apache.org/jira/browse/NIFI-13566
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 2.0.0-M4
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Major
> Fix For: 1.28.0, 2.0.0-M5
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The JettyServer start method has a try/catch with:
> {code:java}
> } catch (Exception ex) {
> startUpFailure(ex);
> } {code}
> Some errors that can happen do not extend Exception so they are not caught
> here, and as a result they do not go into the helper method which calls
> System.exit, so the NiFi process and JettyServer remain started, but in a
> strange non-fully working state.
> It will ultimately bounce to the NiFi main method which just logs the error,
> but doesn't exit:
> {code:java}
> try {
> NiFiProperties properties =
> convertArgumentsToValidatedNiFiProperties(args);
> new NiFi(properties);
> } catch (final Throwable t) {
> LOGGER.error("Failure to launch NiFi", t);
> } {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
