-
Notifications
You must be signed in to change notification settings - Fork 53
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: Error with RunReachabilityHandlersConcurrently build argument #1344
Comments
Thank you for your investigation @ddobrin! Sharing some findings here after testing this out. Unfortunately, it appears that the issue persists when
I'm also able to reproduce the same issue when running tests in java-datatore ( |
From conversation in googleapis/gax-java#1815 (comment): The GraalVM team is tracking this issue(oracle/graal#5194) and will follow up on their findings. Will keep an eye on it in the meantime. |
Thanks for the update. |
The fix for the original issue was merged and added as a milestone for the upcoming feature release - |
FYI:
I have also opened a backport PR to get the fix in 22.3.3 as well . |
Thanks so much for the heads up and putting up the PR @zakkak! |
GraalVM 22.3.3 is also released now, rendering @mpeddada1 is there anything preventing it's removal? What are the GraalVM versions that |
Hi @zakkak, we've merged the PR that removes this argument: #1892. It will be included in release 2.25.0 of this repo. |
Great, thanks for the update @mpeddada1! |
@zakkak @ddobrin Thanks for your patience. This change is now part of libraries-bom:26.23.0! |
In GraalVM, while upgrading to 22.2 the team had to disable concurrent reachability since it was causing some failures in the client libraries when building native images: Issue.
In GraalVM, latest versions (22.3.0 and 22.3.1), disabling the RunReachabilityHandlersConcurrently build argument introduces the need to add a number of additional dependencies (rome tools and kotlinx). GraalVM has it turned on by default.
The issue can be alleviated by reenabling the build argument in an application.
Reproducer: https://github.com/ddobrin/serverless-photosharing-workshop/tree/master/services/image-analysis/java
Tested with the latest BOM version as of today: 26.7.0.
The ask: Could the issue be re-validated in the client libraries with GraalVM 22.3.x to ascertain whether the flag is still creating an issue?
Thank you
The text was updated successfully, but these errors were encountered: