[
https://issues.apache.org/jira/browse/CAMEL-23225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18068197#comment-18068197
]
Guillaume Nodet commented on CAMEL-23225:
-----------------------------------------
_Claude Code on behalf of Guillaume Nodet_
Merged PR https://github.com/apache/camel/pull/22190 which addresses the
general Camel side: propagating OpenTelemetry context across thread boundaries
in camel-opentelemetry2 by porting the thread pool instrumentation from the
deprecated camel-opentelemetry module.
Keeping this issue open as the Spring Boot-specific side still needs to be
addressed — the {{ThreadPoolTaskExecutor}} used in
{{camel-platform-http-starter}} doesn't wrap new threads with the OTel context.
Possible approaches:
* Setting {{spring.reactor.context-propagation=auto}} (see [Spring Boot
docs|https://docs.spring.io/spring-boot/reference/actuator/observability.html#actuator.observability.context-propagation])
* Registering a {{TaskDecorator}} bean in the camel spring-boot starters that
captures and propagates the OTel context
> Spring Boot's default ThreadPoolTaskExecutor doesn't propagate OpenTelemetry
> Context
> ------------------------------------------------------------------------------------
>
> Key: CAMEL-23225
> URL: https://issues.apache.org/jira/browse/CAMEL-23225
> Project: Camel
> Issue Type: Bug
> Components: camel-opentelemetry
> Reporter: John Poth
> Assignee: Guillaume Nodet
> Priority: Major
>
> When using camel-opentelemetry-starter (and v2), let's propagate the
> OpenTelemetry context in Spring Boot's default ThreadPoolTaskExecutor (used
> in camel-platform-http-starter). This causes context leaks
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
