-
-
Notifications
You must be signed in to change notification settings - Fork 809
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
Java 22 Support #1609
Comments
Java 22 is supported in the latest version. You would need to ask the library for an update. |
Awesome thank you! |
@raphw , Hi Rafael, I'm currently maintaining BlockHound, and I have upgraded BlockHound 1.0.9 snapshot with latest bytebuddy version (1.14.13). For the moment, I cannot say from where the problem is. Can you please give a try to the reproducer ? it works well with all jdk versions, except with jdk 22.
install JDK 21 build and run tests (should be successful): try to run the sample application with blockhound agent:
then the exception is correctly thrown by BlockHound:
install jdk 22
actually, it's the BlockHound installation that fails, because when it is installing, it tries to verify if instrumentation is working, see here. (the test is using the special '-XX:+AllowRedefinitionToAddDeleteMethods option, see build.gradle).
I'm investigating, but that would be nice if you could play with the reproducer , maybe you will figure out somethikng ? (the assertions errors from the jdk are very strange ?) thanks ! |
Quite honestly, this looks like a JVM bug to me that is related to |
Thank you Rafael; in fact, I tend to do agree, because I managed to hack BlockHound in order to instrument only one single non-native method, and in this case, it works well with JDK 22. Now, looking into JDK 22, the Thank you. |
Any idea for Java 22 support.
jHipster uses Blockhound for unit testing, which in turn uses byte-buddy. Tests are failing with,
was able to move forward with the vm argument (reactor.blockhound.shaded.net.bytebuddy.experimental).
Also found a similar issue related to Java 21
The text was updated successfully, but these errors were encountered: