-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
None
-
None
-
None
-
Tracing Sprint #33, Tracing Sprint #34
Upstream issue: https://github.com/jaegertracing/jaeger/issues/1819
Need to understand whether this is a reproducible issue with Kafka 2.3, and whether it affects AMQ currently or would in the future.