[
https://issues.apache.org/jira/browse/MINIFI-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Percivall resolved MINIFI-42.
------------------------------------
Resolution: Fixed
> ConfigTransformer does not honor Remote Process Group name/id
> -------------------------------------------------------------
>
> Key: MINIFI-42
> URL: https://issues.apache.org/jira/browse/MINIFI-42
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Processing Configuration
> Reporter: Aldrin Piri
> Assignee: Aldrin Piri
>
> The config YAML uses the Remote Process Group name to establish identity for
> the associated process group with the introduction of supporting multiple
> such groups. If this does not coincide with the Remote-Process-Group name,
> there will be issues when trying to provide the appropriate connections as
> evidenced by stacktraces such as:
> {quote}
> 2016-06-27 10:22:30,242 WARN [main] org.apache.nifi.web.server.JettyServer
> Failed to start web server... shutting down.
> org.apache.nifi.controller.FlowSynchronizationException:
> java.lang.NullPointerException
> at
> org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:317)
> ~[nifi-framework-core-0.6.1.jar:0.6.1]
> {quote}
> or
> {quote}
> java.lang.Exception: Unable to load flow due to:
> org.apache.nifi.controller.FlowSynchronizationException:
> java.lang.RuntimeException: Found Invalid Connectable ID for Destination:
> 8644cbcc-a45c-40e0-964d-5e536e2ada61
> at org.apache.nifi.minifi.MiNiFiServer.start(MiNiFiServer.java:92)
> [minifi-runtime-0.0.1-SNAPSHOT.jar:0.0.1-SNAPSHOT]
> at org.apache.nifi.minifi.MiNiFi.<init>(MiNiFi.java:133)
> [minifi-runtime-0.0.1-SNAPSHOT.jar:0.0.1-SNAPSHOT]
> at org.apache.nifi.minifi.MiNiFi.main(MiNiFi.java:228)
> [minifi-runtime-0.0.1-SNAPSHOT.jar:0.0.1-SNAPSHOT]
> Caused by: org.apache.nifi.controller.FlowSynchronizationException:
> java.lang.RuntimeException: Found Invalid Connectable ID for Destination:
> 8644cbcc-a45c-40e0-964d-5e536e2ada61
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)