[
https://issues.apache.org/jira/browse/NIFI-10369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17607215#comment-17607215
]
Akshara Uke commented on NIFI-10369:
------------------------------------
The issue comes due to the output port defined in the 'test' process group.
Quoting the User Guide
----
!https://nifi.apache.org/docs/nifi-docs/html/images/iconOutputPort.png|width=32!
{*}Output Port{*}: Output Ports provide a mechanism for transferring data from
a Process Group to destinations outside of the Process Group. When an Output
Port is dragged onto the canvas, the DFM is prompted to name the Port. All
Ports within a Process Group must have unique names.
If the Output Port is dragged onto the Root Process Group, the Output Port
provides a mechanism for sending data to remote instances of NiFi via
[Site-to-Site|https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#site-to-site].
In this case, the Port acts as a queue. As remote instances of NiFi pull data
from the port, that data is removed from the queues of the incoming
Connections. If NiFi is configured to run securely, the Output Port can be
configured to restrict access to appropriate users. For information on
configuring NiFi to run securely, see the [System Administrator’s
Guide|https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html].
----
I modified the process group such that the 'test' process group has output port
as a remote output port for site-to-site.
Attached is the template for it - [^testRemote.xml]
Then it started correctly.
If the output port in the 'test' process group is removed, it will start then
as well.
Just to understand the concern, do you propose that the Nifi Sever should start
regardless of the invalid configuration, just log some warning or such?
> Apache NiFi 1.16.x windows server closes immediately
> ----------------------------------------------------
>
> Key: NIFI-10369
> URL: https://issues.apache.org/jira/browse/NIFI-10369
> Project: Apache NiFi
> Issue Type: Bug
> Components: Examples
> Affects Versions: 1.16.3
> Environment: Windows, Linux
> Reporter: Nikolay Akimov
> Priority: Critical
> Labels: test-stability
> Attachments: Output_Port.xml, testRemote.xml
>
>
> When I try to restart the server it's throwing with the following error
> message.
> *org.apache.nifi.controller.serialization.FlowSynchronizationException:
> java.lang.IllegalStateException: Cannot add Connection to Process Group
> because source is an Output Port that does not belong to a child Process
> Group*
>
> I have simplified the scenario to such an extent that it is reproducible. I
> attach the file. After importing this file and if you place the template on
> the canvas, WiFi does not start after the restart.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
