[
https://issues.apache.org/jira/browse/NIFI-15500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-15500.
-----------------------------------
Fix Version/s: 2.8.0
Assignee: Pierre Villard
Resolution: Duplicate
> Azure Blob access no longer works on 2.7.2
> ------------------------------------------
>
> Key: NIFI-15500
> URL: https://issues.apache.org/jira/browse/NIFI-15500
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 2.7.2
> Environment: All
> Reporter: Craig Patrick
> Assignee: Pierre Villard
> Priority: Blocker
> Fix For: 2.8.0
>
>
> Since upgrading to 2.7.2 from 2.0.0, all of our Azure Blob processors have
> failed to work which is causing a major issue for us - the error we are
> seeing is this:
> {code:java}
> PutAzureBlobStorage_v12[id=ea118bcc-019b-1000-c292-55693713826e] Processing
> halted: yielding [1 sec]: java.lang.NoClassDefFoundError: Could not
> initialize class reactor.netty.http.client.HttpClientSecure - Caused by:
> java.lang.ExceptionInInitializerError: Exception
> java.lang.NoClassDefFoundError: io/netty/handler/codec/quic/Quic [in thread
> "Timer-Driven Process Thread-6"]{code}
>
> in the logs on startup, I'm seeing this:
> {code:java}
> 2026-01-23 09:21:23,566 INFO [Timer-Driven Process Thread-9]
> c.a.c.h.n.implementation.NettyUtility {"az.sdk.message":"The following Netty
> versions were found on the classpath and have a mismatch with the versions
> used by azure-core-http-netty. If your application runs without issue this
> message can be ignored, otherwise please align the Netty versions used in
> your application. For more information, see
> https://aka.ms/azsdk/java/dependency/troubleshoot.","azure-netty-version":"4.1.127.Final","azure-netty-native-version":"2.0.74.Final","classpath-netty-version-io.netty:netty-common":"4.2.9.Final","classpath-netty-version-io.netty:netty-handler":"4.2.9.Final","classpath-netty-version-io.netty:netty-handler-proxy":"4.2.9.Final","classpath-netty-version-io.netty:netty-buffer":"4.2.9.Final","classpath-netty-version-io.netty:netty-codec":"4.2.9.Final","classpath-netty-version-io.netty:netty-codec-http":"4.2.9.Final","classpath-netty-version-io.netty:netty-codec-http2":"4.2.9.Final","classpath-netty-version-io.netty:netty-transport-native-unix-common":"4.2.9.Final","classpath-netty-version-io.netty:netty-transport-native-epoll":"4.2.9.Final","classpath-netty-version-io.netty:netty-transport-native-kqueue":"4.2.9.Final","classpath-native-netty-version-io.netty:netty-tcnative-boringssl-static":"2.0.74.Final"}
> {code}
> Is this a known issue, is there a workaround or is this fixed in a patch?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
