OpenTelemetry Context propagation issue with ExecutorService in RHBQ 2.13

Solution Unverified - Updated -

Issue

-We have migrated to OpenTelemetry because RHBQ 2.13 release notes pointed out that smallrye opentracing was deprecated.
But we spotted that in one of our usecase a regression compared to the usage of smallrye-opentracing which is the following :
The OTEL context is not propagated when we use our own ExecutorService but instrumented with ThreadContext propagation.
We created a reproducer available on github ( https://github.com/OpenGuidou/opentelemetry-propagation-reproducer) that is showing that we loose the traceid upon creating a new span in an asynchronous method execution, whereas quarkus bootstraps should ensure the propagation.

Environment

  • Red Hat build of Quarkus
    • 2.13.5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content