-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
com.oracle.svm.core.jdk.UnsupportedFeatureError: ThreadMXBean methods #1039
Comments
Hello, Any updates on this? |
I'm also curious to know if there is an update on this. I'm investigating GraalVM at work and got pretty far but this is a blocker. We use prometheus and their official java-client: https://github.com/prometheus/client_java. It seems to rely on If there is a way to mitigate this, I'd be a taker. I don't know if it's a configuration issue at native-image build time or if it's a problem with the generation itself. |
An update from the Micrometer side (since it is used in the original issue report) is that since Micrometer 1.3.7, the error should not be thrown at runtime. The metrics related to thread states will be unavailable but we handle the error since 1.3.7. See micrometer-metrics/micrometer@6635860. |
Any updates on this? |
It would at least be nice to not throw an uncatchable runtime error for the unimplemented methods, such as an attempt to get a list of threadids. This should certainly be handleable gracefully by caller if a nonfatal exception were thrown instead. |
|
To reproduce the issue:
git clone https://github.com/micronaut-graal-tests/micronaut-management-graal
cd micronaut-management-graal
git checkout threadmxbean
./build-native-image.sh
./management-graal
curl localhost:8080/metrics/jvm.threads.states
Error:
The text was updated successfully, but these errors were encountered: