[
https://issues.apache.org/jira/browse/NIFI-7459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Weghorst updated NIFI-7459:
--------------------------------
Attachment: nifi-7459.patch
Affects Version/s: 1.12.0
Labels: patch pull-request-available (was: )
Status: Patch Available (was: In Progress)
After digging into this, I'm certain that this issue is a side effect of the
stateless runtime not using the NarClassLoader and the lack of runtime
dependency isolation between nar bundles.
This patch changes the stateless class loader implementation to more closely
match the jetty server.
This also required a reorganization of the directory structure of the
stateless-nars work directory in stateless to more closely match the jetty
server. Framework and extensions are now in separate directories.
A PR is available [https://github.com/apache/nifi/pull/4499]
> confluent schema registry controller service wont initialize in stateless
> runtime
> ---------------------------------------------------------------------------------
>
> Key: NIFI-7459
> URL: https://issues.apache.org/jira/browse/NIFI-7459
> Project: Apache NiFi
> Issue Type: Bug
> Components: NiFi Stateless
> Affects Versions: 1.11.4, 1.12.0
> Environment: Docker container created using
> nifi-docker/dockermaven-stateless on an 1.11.4 codebase with
> https://github.com/apache/nifi/pull/4264 (NIFI-7380)
> This patch is necessary to work around an issue with controller services not
> initializing in the stateless runtime. The reproducer has 2 controller
> services.
> Reporter: Mark Weghorst
> Assignee: Mark Weghorst
> Priority: Blocker
> Labels: patch, pull-request-available
> Attachments: confluent-reproducer.xml,
> nifi-7380-confluent-schema-registry-exception.txt, nifi-7459.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The ConfluentSchemaRegistry controller service will not initialize in the
> stateless runtime but works correctly in the server runtime. I've attached a
> template for a flow that reproduces this problem, and the exception generated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
