-
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
[GraalVM 24.0] quarkus-integration-test-hibernate-reactive-postgresql fails to compile due to vertx-sql-client issue with JDK 22 #37208
Comments
Note that this doesn't fail with the GraalVM CE build (using JDK 22+23). So later version of JDK 22 might be related. |
This seems to affect the following native integration tests (on Mandrel 24.0):
|
Yes. This looks like a JDK issue: JDK 22+23 ea:
JDK 22+24 ea
|
I've filed https://bugs.openjdk.org/browse/JDK-8320431 |
OK looks like this is intended behaviour - JDK 22 no longer falls back to COMPAT - and the work-around is to use
Who can help getting this into |
vertx sql client issue is here: eclipse-vertx/vertx-sql-client#1379 |
is that a JVM bug ? |
Hi @vietj, (as mentioned in eclipse-vertx/vertx-sql-client#1379 (comment)) @jerboaa created a JVM bug for it and
So the new behavior (aka getting the exception we see) is intended.
|
Workaround for quarkusio#37208 till eclipse-vertx/vertx-sql-client#1379 gets fixed and released Note that the substitution only happens if necessary (i.e. it won't happen when using JDK < 22, and it won't happen once an upstream fix becomes available. Closes quarkusio#37208
This issue got closed with #38034. We no longer see CI issues related to vertx-sql-client. |
Describe the bug
We see the
quarkus-integration-test-hibernate-reactive-postgresql
native integration test failing using Mandrel 24.0 (GraalVM for JDK 22) with the following error:See:
https://github.com/graalvm/mandrel/actions/runs/6924384895/job/18834111016#step:12:865
Root cause seems to be:
Output of
java -version
22+24 (ea)
Quarkus version or git rev
main
The text was updated successfully, but these errors were encountered: