-
Notifications
You must be signed in to change notification settings - Fork 66
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
Failed to bind after upgrading to java 21 #679
Comments
It looks like Micrometer does not provide any instrumentation for an I think the appropriate thing for us to do is detect usage of virtual threads in our Given that, I believe this particular warning can be safely ignored in the meantime. |
ExecutorServiceMetricsBinder is updated to not attempt to bind ExecutorServiceMetrics to a ThreadPerTaskExecutor which is used in the case of virtual threads and is not supported by ExecutorServiceMetrics. Resolves #679
ExecutorServiceMetricsBinder is updated to not attempt to bind ExecutorServiceMetrics to a ThreadPerTaskExecutor which is used in the case of virtual threads and is not supported by ExecutorServiceMetrics. Resolves #679
Thank you @jeremyg484 :) |
I still get this warning with Micronaut platform 4.3.7, micronaut-micrometer 5.4.0 |
It did not end up getting included in the 4.3.x releases as we've not done an updated release of this module yet. It should definitely get included in 4.4.0. |
Expected Behavior
The application should have started without logging a warning
Actual Behaviour
After application was configured to use java 21 - at startup, the application logs this warning:
Not sure if this is a micronaut or a micrometer issue.
Steps To Reproduce
No response
Environment Information
Operating system: Linux
JDK: 21 (coretto)
Example Application
No response
Version
4.2.2
The text was updated successfully, but these errors were encountered: