[
https://issues.apache.org/jira/browse/CAMEL-23283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18071632#comment-18071632
]
Pasquale Congiusti commented on CAMEL-23283:
--------------------------------------------
Hello, thanks for looking into this issue and put togheter a possible solution.
However, the proposed solution breaks the original design. Reading the
description I don't exactly get what is the issue is. The component is in
charge to provide context propagation transparently, and you cannot get the
current trace during the route execution because this is added and removed
dynamically during the execution of each exchange. If you can put togheter a
simple reproducer to show exactly the issue, I can give a look and we can
reason about the best solution according the component design.
> OpenTelemetry/Micrometer traces are not exported for JMS-initiated routes
> -------------------------------------------------------------------------
>
> Key: CAMEL-23283
> URL: https://issues.apache.org/jira/browse/CAMEL-23283
> Project: Camel
> Issue Type: Bug
> Components: camel-tracing
> Affects Versions: 4.15.0, 4.16.0, 4.17.0, 4.18.0, 4.18.1
> Reporter: Bjorn Beskow
> Priority: Major
>
> When using camel-observability or camel-micrometer-observability, traces and
> spans are correctly created and exported for routes triggered by other,
> tracing-aware framework components (e.g. http). If a route is triggered by a
> jms message, no trace or span is exported however.
> This seems to be caused by missing scope management:
> MicrometerObservabilitySpanAdapter::activate() only calls span.start() but
> doesn't put the
> span into the tracer's thread-local scope. This means tracer.currentSpan()
> returns null during route execution, hence the span is invisible to
> downstream instrumentation that relies on tracer.currentSpan() to find a
> parent span.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
