You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2015/02/23 17:20:11 UTC
[jira] [Created] (NIFI-373) If NiFi UI is secure but cluster
communication is not, NiFi doesn't start but throws NullPointer instead of
nice error message
Mark Payne created NIFI-373:
-------------------------------
Summary: If NiFi UI is secure but cluster communication is not, NiFi doesn't start but throws NullPointer instead of nice error message
Key: NIFI-373
URL: https://issues.apache.org/jira/browse/NIFI-373
Project: Apache NiFi
Issue Type: Bug
Components: Core Framework
Reporter: Mark Payne
If using HTTPS protocol instead of HTTP protocol (i.e., the 'nifi.web.https.port' property is defined in the nifi.properties file), NiFi throws a NullPointerException. This needs to instead provide a pretty error message.
In general, any time we attempt to retrieve an integer property, if not set, we should throw an exception indicating that the property is not set, rather than throwing NullPointerException.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)