You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using quarkus-messaging-kafka, with snappy enabled (quarkus.kafka.snappy.enabled=true), it fails to start on native on architecture aarch64, with exception
java.lang.RuntimeException: Failed to start quarkus
at io.quarkus.runner.ApplicationImpl.doStart(Unknown Source)
at io.quarkus.runtime.Application.start(Application.java:101)
at io.quarkus.runtime.ApplicationLifecycleManager.run(ApplicationLifecycleManager.java:119)
at io.quarkus.runtime.Quarkus.run(Quarkus.java:71)
at io.quarkus.runtime.Quarkus.run(Quarkus.java:44)
at io.quarkus.runtime.Quarkus.run(Quarkus.java:124)
at io.quarkus.runner.GeneratedMain.main(Unknown Source)
Caused by: java.lang.RuntimeException: no native library is found for os.name=Linux and os.arch=aarch64
at io.quarkus.kafka.client.runtime.SnappyRecorder.getLibraryFile(SnappyRecorder.java:45)
at io.quarkus.kafka.client.runtime.SnappyRecorder.loadSnappy(SnappyRecorder.java:26)
at io.quarkus.deployment.steps.KafkaProcessor$loadSnappyIfEnabled133026306.deploy_0(Unknown Source)
at io.quarkus.deployment.steps.KafkaProcessor$loadSnappyIfEnabled133026306.deploy(Unknown Source)
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Output of uname -a or ver
No response
Output of java -version
No response
Mandrel or GraalVM version (if different from Java)
No response
Quarkus version or git rev
No response
Build tool (ie. output of mvnw --version or gradlew --version)
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
@cescoffier if I get this right #40304 is only meant for JVM mode, so restricting it to JVM-mode and applying something like #43782 in native-mode wouldn't break it, right?
We started receiving more demands to include native libraries for other os/arch (not only the host one). I will start a discussion on Monday as we need to discuss how we can handle that and the consequences on native compilation.
Always registers the correct native library as the logic runs on the
same architecture we are targeting (even when using containers).
Closesquarkusio#43801
(cherry picked from commit b9ec68c)
Describe the bug
When using quarkus-messaging-kafka, with snappy enabled (
quarkus.kafka.snappy.enabled=true
), it fails to start on native on architecture aarch64, with exceptionExpected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
Mandrel or GraalVM version (if different from Java)
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: