-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Native build error on Quarkus 2.2.1.Final when using Opentelemetry #19877
Labels
Milestone
Comments
/cc @geoand, @iocanel, @kenfinnigan |
There are two separate issues here. |
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Sep 3, 2021
Essentially the fact that ClientTracingFilter was using a static field for TextMapPropagator was causing GraalVM to initialize the entire telemetry infrastructure at build time Fixes: quarkusio#19877
#19897 is the fix for the main issue |
kenfinnigan
pushed a commit
to kenfinnigan/quarkus
that referenced
this issue
Sep 3, 2021
Essentially the fact that ClientTracingFilter was using a static field for TextMapPropagator was causing GraalVM to initialize the entire telemetry infrastructure at build time Fixes: quarkusio#19877
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Sep 6, 2021
Essentially the fact that ClientTracingFilter was using a static field for TextMapPropagator was causing GraalVM to initialize the entire telemetry infrastructure at build time Fixes: quarkusio#19877 (cherry picked from commit d142b2f)
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Sep 6, 2021
Essentially the fact that ClientTracingFilter was using a static field for TextMapPropagator was causing GraalVM to initialize the entire telemetry infrastructure at build time Fixes: quarkusio#19877 (cherry picked from commit d142b2f)
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Sep 6, 2021
Essentially the fact that ClientTracingFilter was using a static field for TextMapPropagator was causing GraalVM to initialize the entire telemetry infrastructure at build time Fixes: quarkusio#19877 (cherry picked from commit d142b2f)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
In migrating a Quarkus app from 2.1.2.Final to 2.2.1.Final an NPE occurs in the
io.quarkus.opentelemetry.runtime.QuarkusContextStorage.getVertxContext()
method during native build, causing the build to fail.Expected behavior
The native build should complete successfully.
Actual behavior
The following error occurs:
How to Reproduce?
A reproducer git project may be found here; in summary the following is a minimal set required to reproduce the error:
quarkus-opentelemetry-exporter-otlp
(I needed a few others to be included, perhaps to stimulate the otel SDK into doing something, but this appears to be the main trigger)e.g. the following interface
And application.yaml:
Its possible some other dependencies are required, but this seems to be the heart of the repro. FWIW these were the full list of dependencies I ended up with in the pom:
Output of
uname -a
orver
MINGW64_NT-10.0-18363 LAP1453 3.0.7-338.x86_64 2019-04-30 21:52 UTC x86_64 Msys
Output of
java -version
openjdk version "11.0.11" 2021-04-20 OpenJDK Runtime Environment GraalVM CE 21.1.0 (build 11.0.11+8-jvmci-21.1-b05) OpenJDK 64-Bit Server VM GraalVM CE 21.1.0 (build 11.0.11+8-jvmci-21.1-b05, mixed mode, sharing)
GraalVM version (if different from Java)
OpenJDK Runtime Environment GraalVM CE 21.2.0 (build 11.0.12+6-jvmci-21.2-b08)
Quarkus version or git rev
2.2.1.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
Additional information
No response
The text was updated successfully, but these errors were encountered: