[CAMEL-21472] Opentelemetry is using the same traceId when exchange is fired from file or timer component

• Type: Bug
• Status: In Progress
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 4.8.1
• Fix Version/s: 4.8.3, 4.10.0
• Component/s: camel-opentelemetry
• Estimated Complexity: Unknown
• Assignee: Pasquale Congiusti
• Reporter: Thomas Gantenbein
• Created: 6 days ago 12:34
• Updated: Yesterday 19:41

Description

Problem

When using a consumer like timer or file, the traceId remains the same for all messages. When using a consumer like netty (or, I assume, any other http/tcp-based consumer), every call gets its own traceId as expected.

See also https://camel.zulipchat.com/#narrow/channel/257298-camel/topic/Same.20OTEL.20trace.20for.20all.20messages.20into.20IBM.20MQ

Reproducer

https://github.com/thomas-gantenbein-tga/camel-opentelemetry/tree/main

Pasquale Congiusti, thanks for your answer on Zulip Chat. Let me know if I should further explain or minimize that reproducer.

Issue Links

• links to: GitHub Pull Request #16386