-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Native image build with quarkus-infinispan-client and quarkus-grpc #12460
Comments
/cc @michalszynkiewicz, @cescoffier |
The error:
|
Ispn client brings in
|
@cescoffier I remember seeing some discussions about trying to add support for native-epoll to quarkus native. Is this correct? Here's how it's defined for ispn-hotrod-client: |
So far, epoll in native is not supported. @galderz is working on it and is making tremendous progress. However, still not there. |
BTW, we can't exclude the dependencies as it works perfectly well in JVM mode. |
By So I guess we want a way to stop Netty from figuring out that epoll is available when it runs in the native mode, right? |
Exactly. We still want to support the epoll native transport in JVM mode. But in native mode, we need to be sure it's not enabled. In Vert.x, I have a substitution that disables it, we may need to do the same in gRPC. |
Describe the bug
When trying to build a native image using a docker container on Windows from an application that uses quarkus-infinispan-client and quarkus-grpc the buildfails with Error: Classes that should be initialized at run time got initialized during image building: with a list netty classes.
Expected behavior
The build succeeds.
Actual behavior
The build fails with a list of netty classes , also a lot of wildfly duplicates are listed before.
To Reproduce
Steps to reproduce the behavior:
Configuration
application.properties is empty as generated
Screenshots
Environment (please complete the following information):
uname -a
orver
:Microsoft Windows [Version 10.0.19041.508]
java -version
:openjdk version "11.0.5" 2019-10-15
OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.5+10)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.5+10, mixed mode)
No GraalVM
1.8.1.Final (but happens in previous releases also)
mvnw --version
orgradlew --version
):mvnw
Additional context
No additional context
The text was updated successfully, but these errors were encountered: