[
https://issues.apache.org/jira/browse/NIFI-13757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882560#comment-17882560
]
ASF subversion and git services commented on NIFI-13757:
--------------------------------------------------------
Commit 44abe3998317e8f6ecd49f42a80c53addb97d8ad in nifi's branch
refs/heads/main from Bryan Bende
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=44abe39983 ]
NIFI-13757 Improve handling when a NAR contains an extension that produces an
Error (#9274)
Signed-off-by: David Handermann <[email protected]>
> Uploaded NAR hits Error and stays Installing
> --------------------------------------------
>
> Key: NIFI-13757
> URL: https://issues.apache.org/jira/browse/NIFI-13757
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The NarInstallTask has a try/catch for Exception, but in some cases
> attempting to load the actual extension class may produce a sub-class of
> Error which is not caught by the task, so then the state never gets updated
> to FAILED and the error message never gets set.
> In addition, at the point during which it hits the Error, the NAR has already
> been registered in ExtensionManager, and future calls to get available
> extension types will see the bundle and attempt to access the extension
> definitions, which also encounters the same Error and fails the overall
> request. This should be made more lenient to still allow all the other
> available extensions to be returned.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
