-
Notifications
You must be signed in to change notification settings - Fork 843
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
In a modular application, sun.misc.Unsafe
is a problem
#6913
Comments
More context: On that version, you'll get this on startup:
But everything works anyway. |
Thanks @io7m for the submission. Please see the discussion in #6433 for some gory details about this. As I understood things, this should have been guarded against in JDKs where Unsafe is no longer available (like the jdk 23 you were using). Am I safe in assuming that there is something different/special in the way you're using the module path instead of just classpath? Would you be able to provide a repo that reproduces this error? |
To my knowledge, I'm not doing anything special. The application is fully modularized and places all of its own jars and dependencies (including OpenTelemetry) on the module path. The application in question is this one: https://github.com/io7m-com/cardant You should just be able to The build produces a zip
If any of this is a problem, I can try to get something smaller together. |
Describe the bug
When running an application that exclusively uses the module path, and places its own modules plus those of OpenTelemetry on the module path, I get errors like this:
Previously, I'd get a warning about a missing
sun.misc.Unsafe
class, but everything would still work correctly.Steps to reproduce
It seems like placing the OpenTelemetry artifacts on the module path is enough to trigger this.
What did you expect to see?
No exceptions.
What did you see instead?
A rather nasty exception, and no telemetry being sent.
What version and what artifacts are you using?
1.44.1
.https://github.com/io7m-com/cardant/blob/db0178a55f80d2a5f729da6cb22af56ebdfa5a94/pom.xml#L530
Environment
The text was updated successfully, but these errors were encountered: