nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (MINIFI-428) Issues with serialization on startup
Date Thu, 18 Jan 2018 17:29:00 GMT


ASF GitHub Bot commented on MINIFI-428:

GitHub user apiri opened a pull request:

    MINIFI-428 Create an empty FlowRegistryClient

    MINIFI-428 Create an empty FlowRegistryClient instead of a null reference.
    Thank you for submitting a contribution to Apache NiFi - MiNiFi.
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    ### For all changes:
    - [X] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    - [X] Does your PR title start with MINIFI-XXXX where XXXX is the JIRA number you are
trying to resolve? Pay particular attention to the hyphen "-" character.
    - [X] Has your PR been rebased against the latest commit within the target branch (typically
    - [X] Is your initial contribution a single, squashed commit?
    ### For code changes:
    - [X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check
clean install at the root nifi-minifi folder?
    - [-] Have you written or updated unit tests to verify your changes?
    - [-] If adding new dependencies to the code, are these dependencies licensed in a way
that is compatible for inclusion under [ASF 2.0](

    - [-] If applicable, have you updated the LICENSE file, including the main LICENSE file
under minifi-assembly?
    - [-] If applicable, have you updated the NOTICE file, including the main NOTICE file
found under minifi-assembly?
    ### For documentation related changes:
    - [-] Have you ensured that format looks appropriate for the output in which it is rendered?
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible.

You can merge this pull request into a Git repository by running:

    $ git pull MINIFI-428

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #111
commit 0bbb4323a9cb42e4510bde0f58b4950eea1582df
Author: Aldrin Piri <aldrin@...>
Date:   2018-01-17T13:00:04Z

    MINIFI-426-RC1 prepare release minifi-0.4.0-RC1

commit f8827305303bf474d7a6bff3810e0863895366e6
Author: Aldrin Piri <aldrin@...>
Date:   2018-01-17T13:00:14Z

    MINIFI-426-RC1 prepare for next development iteration


> Issues with serialization on startup
> ------------------------------------
>                 Key: MINIFI-428
>                 URL:
>             Project: Apache NiFi MiNiFi
>          Issue Type: Bug
>          Components: Agent Configuration/Installation
>    Affects Versions: 0.4.0
>            Reporter: Aldrin Piri
>            Assignee: Aldrin Piri
>            Priority: Blocker
>             Fix For: 0.4.0
> As reported in the RC1 0.4.0 vote, there are issues with startup and some configs.
> {code:java}
> 2018-01-18 11:31:40,743 WARN [main] org.apache.nifi.minifi.MiNiFiServer
> Failed to start minifi server... shutting down.
> java.lang.Exception: Unable to load flow due to:
> java.lang.NullPointerException
> at org.apache.nifi.minifi.MiNiFiServer.start(
> at org.apache.nifi.minifi.MiNiFi.<init>(
> at org.apache.nifi.minifi.MiNiFi.main(
> Caused by: java.lang.NullPointerException: null
> at
> org.apache.nifi.controller.serialization.StandardFlowSerializer.addFlowRegistries(
> at
> org.apache.nifi.controller.serialization.StandardFlowSerializer.serialize(
> at
> org.apache.nifi.controller.FlowController.serialize(
> at
> at
> at
> org.apache.nifi.persistence.StandardXMLFlowConfigurationDAO.load(
> at
> org.apache.nifi.controller.StandardFlowService.loadFromBytes(
> at
> org.apache.nifi.controller.StandardFlowService.load(
> at org.apache.nifi.minifi.MiNiFiServer.start(
> ... 2 common frames omitted
> {code}

This message was sent by Atlassian JIRA

View raw message