[
https://issues.apache.org/jira/browse/NIFI-8614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351351#comment-17351351
]
ASF subversion and git services commented on NIFI-8614:
-------------------------------------------------------
Commit 103aae64cb28de235983880ba2b78f935ca56767 in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=103aae6 ]
NIFI-8614 Adjusted NodeClusterCoordinatorFactoryBean to handle null
ClusterNodeFirewall (#5100)
- Changed FileBasedClusterNodeFirewallFactoryBean to return null when
configuration file is not found
> Null Cluster Node Firewall fails to start on Spring 5
> -----------------------------------------------------
>
> Key: NIFI-8614
> URL: https://issues.apache.org/jira/browse/NIFI-8614
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.14.0
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Blocker
> Fix For: 1.14.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Following the upgrade to Spring Framework 5 in NIFI-8502, a cluster node can
> fail start due to a null {{ClusterNodeFirewall}} object. The
> {{FileBasedClusterNodeFirewallFactoryBean}} returns null when no
> configuration file exists, which causes ApplicationContext.getBean() to
> return a {{NullBean}} in {{NodeClusterCoordinatorFactoryBean}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
