[jira] [Created] (NIFI-13566) JettyServer remains started when a ClassNotFoundError happens

["Bryan Bende (Jira)" <ji...@apache.org>]

Bryan Bende created NIFI-13566:
----------------------------------

             Summary: 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


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)