-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Using OpenTelemetry gRPC instrumentation produces NullPointerException when running quarkusBuild #22864
Comments
Ensure that the presence of OpenTelemetry does not break Jib builds
Fixes: quarkusio#22864 (cherry picked from commit b6a693c)
I found a similar issue when running a test that will use gRPC client even using Quarkus Error logs:
|
Maybe using #22865 could fix these kinds of issues once for all? It could stop |
Yeah, but #22866 is not working for this new situation by disable otel while pulling image.
I am curious why #22865 is not the proper solution. It fixed a potential nullpointer error, and it can also fix the old issue. (Not testing the new one) |
I know, I never said it would fix your latest issue. What I am saying is that the root cause is similar.
Because it's just a bandaid. We don't want arbitrary Vert.x contexts popping up out of nowhere. |
Adding |
Describe the bug
Using io.opentelemetry.instrumentation:opentelemetry-grpc-1.6:1.9.2-alpha and
io.quarkus:quarkus-opentelemetry-exporter-otlp
with Quarkus 2.6.2.Final producesNullPointerException
when packaging image byquarkusBuild
.Expected behavior
It should produce an image without error.
Actual behavior
How to Reproduce?
gradle.properties
file./gradlew quarkusBuild
Output of
uname -a
orver
21.2.0
Output of
java -version
openjdk version "16.0.1" 2021-04-20 OpenJDK Runtime Environment (build 16.0.1+9-24) OpenJDK 64-Bit Server VM (build 16.0.1+9-24, mixed mode, sharing)
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.6.2.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)Gradle 7.3.3
Additional information
No response
The text was updated successfully, but these errors were encountered: