-
Notifications
You must be signed in to change notification settings - Fork 870
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
spring-native example fails to build with GraalVM 22 #12416
Comments
I stumbled upon this issue as well. It doesn't feel right to tune build process by having any updates on this one? ETA? |
@super7ramp maybe this ticket should be reported in different repo of the OTEL. This repo is just for the examples and maybe it doesn't have the traction and the attention. |
@super7ramp could you please provide a link to the GraalVM you've used to successfully build this? |
@jack-berg could this problem be related to the open-telemetry/opentelemetry-java#6127 and similar solution as open-telemetry/opentelemetry-java#6139 could be applied for the java instrumentation https://github.com/open-telemetry/opentelemetry-java-instrumentation? |
cc @jeanbisutti |
transferring to instrumentation repo at @jeanbisutti's request |
@super7ramp Thank you for reporting this issue. We need to do changes in the OpenTelemetry starter to make it work without any user configuration. |
spring-native example fails to build with GraalVM 22. It builds fine with GraalVM 21.
Errors found in build logs:
Full logs
Adding
--trace-object-instantiation=io.opentelemetry.instrumentation.api.internal.cache.MapBackedCache
as suggested in the logs gives:Adding
--initialize-at-run-time=io.opentelemetry.instrumentation.logback.appender.v1_0.internal.LoggingEventMapper
gives:Excluding native configuration with the following arguments makes the build pass but I'm not sure it's the right thing to do:
The text was updated successfully, but these errors were encountered: