You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2015/06/03 17:25:38 UTC
[jira] [Updated] (NIFI-373) If NiFi UI is secure but cluster
communication is not, NiFi doesn't start but throws NullPointer instead of
nice error message
[ https://issues.apache.org/jira/browse/NIFI-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joseph Witt updated NIFI-373:
-----------------------------
Fix Version/s: 0.1.1
> 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
> Labels: beginner, newbie
> Fix For: 0.1.1
>
>
> 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)