[
https://issues.apache.org/jira/browse/NIFI-9310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17431303#comment-17431303
]
ASF subversion and git services commented on NIFI-9310:
-------------------------------------------------------
Commit 90ae271692af69b2be99f32388a3088e19ef1cdd in nifi's branch
refs/heads/main from markap14
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=90ae271 ]
NIFI-9310: Addressed issues found while testing the component verification
features. Added a supportsVerification flag to the ConfigAnalysis DTO (#5469)
This closes #5469
> Failure to perform component verification prevented UI from responding
> ----------------------------------------------------------------------
>
> Key: NIFI-9310
> URL: https://issues.apache.org/jira/browse/NIFI-9310
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.15.0
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Blocker
> Fix For: 1.15.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This issue does not affect any released versions, but it needs to be
> addressed before we release.
> When component configuration is verified, the method that gets called on
> NiFiServiceFacade is verifyProcessorConfiguration,
> verifyControllerServiceConfiguration, verifyReportingTaskConfiguration.
> But the verify* methods of the NiFiServiceFacade hold a lock due to the
> Around Advice implemented by NiFiServiceFacadeLock.
> The lock should not be held in this case. We should instead rename the
> methods to performProcessorConfigVerification,
> performControllerServiceConfigVerification,
> performReportingTaskConfigVerification in order to avoid holding a lock.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
