[jira] [Commented] (NIFI-373) If NiFi UI is secure but cluster communication is not, NiFi doesn't start but throws NullPointer instead of nice error message

["Joseph Witt (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14597518#comment-14597518 ] 

Joseph Witt commented on NIFI-373:
----------------------------------

Code looks good.  Patch applied cleanly.  Full clean build with contrib-check all good.

+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
>            Assignee: Matt Gilman
>              Labels: beginner, newbie
>             Fix For: 0.2.0
>
>         Attachments: 0001-NIFI-373.patch
>
>
> 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)