StackdriverTraceExporter exceptions with "Panic! This is a bug!" #1963
Comments
|
There seem to be two issues here:
|
|
The AbstractMethodError looks to be because grpc is getting included twice in the build: once via http_archive()/java_grpc_library() and another time via maven_install() (via I tried to reproduce but couldn't. maven_install(
...
override_targets = {
"io.grpc:grpc-alts": "@io_grpc_grpc_java//alts",
"io.grpc:grpc-auth": "@io_grpc_grpc_java//auth",
"io.grpc:grpc-context": "@io_grpc_grpc_java//context",
"io.grpc:grpc-core": "@io_grpc_grpc_java//core",
"io.grpc:grpc-grpclb": "@io_grpc_grpc_java//grpclb",
"io.grpc:grpc-netty-shaded": "@io_grpc_grpc_java//netty",
"io.grpc:grpc-protobuf": "@io_grpc_grpc_java//protobuf",
"io.grpc:grpc-protobuf-lite": "@io_grpc_grpc_java//protobuf-lite",
"io.grpc:grpc-stub": "@io_grpc_grpc_java//stub",
},
...
)Note that //netty isn't fully equivalent to grpc-netty-shaded. They have different package names (which should generally be okay; libraries should not refer to any of grpc-netty/grpc-netty-shaded's APIs because they are unstable) but also grpc-netty-shaded includes netty tcnative. So I also needed to add |
|
@ejona86 your |
This can be used to prevent duplicate classes in the classpath, one via Maven and one via Bazel-native. See census-instrumentation/opencensus-java#1963 and grpc#5359
This can be used to prevent duplicate classes in the classpath, one via Maven and one via Bazel-native. See census-instrumentation/opencensus-java#1963 and #5359
|
Fix has been made to upstream. Mark this issue as resolved for now. |
What version of OpenCensus are you using?
0.23.0
What JVM are you using (
java -version)?What did you do?
If possible, provide a recipe for reproducing the error.
I've created a small repository to demonstrate the issue, here. From the root of the repository run
bazel run //:echo. You will see something like:if you have existing Google Credentials (please be aware that this may write traces into your account). Note the last line:
SEVERE: Span Sent.com.google.api.client.http.HttpRequest.execute is GC'ed without being ended.To trigger the issue either wait for enough traces to buffer or send traffic to force the issue. I do the following:
Running ghz from the root of the
echoproject.What did you expect to see?
I expected to see traces in the Stackdriver Trace console.
What did you see instead?
Additional context
I'm unsure if this issue is related to the one I present in #1962. I ran into this issue trying to build a small reproducible case but hit this instead.
The text was updated successfully, but these errors were encountered: