-
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
Warnings about brotli in quarkus-netty when compiled with Mandrel 24.2 (JDK 24+15) or better #43538
Comments
/cc @Karm (mandrel), @cescoffier (netty), @franz1981 (netty), @galderz (mandrel), @jponge (netty), @zakkak (mandrel) |
There is this tid-bit on the codebase: quarkus/extensions/netty/runtime/pom.xml Lines 65 to 73 in f0762e4
|
We will have to go with the second option. |
I'm pretty surprised that we have such hard dep - it looks to me to be optional for the http/http2 codecs - and looks to use an holder pattern to avoid initializing |
@franz1981 It is configurable, but perfectly sane option and something expected of any contemporary webserver... |
I created #43556 to explore that possibility (to my understanding it's possible but requires some Quarkus "magic") |
Although this bug was detecting using Mandrel, it's not limited to native compilation. See #44257. Once #44257 and oracle/graal#10008 get addressed this issue should be fixed as well. |
Describe the bug
https://openjdk.org/jeps/472 got included with JDK 24. This means that JNI access will produce warnings when run with JDK 24 and certain restricted methods get called. This warning shows up with a Mandrel build using JDK 24+15 EA for example when compiling the getting started quickstart:
The warning produced by the JDK is:
Example of an native image build where the warning happens:
Expected behavior
No warning from brotli when generating the native image.
Actual behavior
A warning is produced
How to Reproduce?
Output of
uname -a
orver
Linux x86_64
Output of
java -version
JDK 24+15
Quarkus version or git rev
main
Build tool (ie. output of
mvnw --version
orgradlew --version
)maven
Additional information
There seem to be at least two options moving forward:
--enable-native-access=ALL-UNNAMED
to the native image buildThe text was updated successfully, but these errors were encountered: