I'm using the following libraries:
-Define JmsComponent as a Spring bean:
@Bean(name = "core-jms")
public JmsComponent createJmsComponentBean(
@Qualifier(value = "core-jmsConnectionFactory") ConnectionFactory connectionFactory) throws JMSException
If you use this JmsComponent in your route (like: from("core-jms://...) then the protocol name change from jms:// into core-jms:// and the current registered SpanDecorators wont match with this one. What will result into wrong tracing id's among the whole flow.
Thus let's say we have the following situation:
Route A -> Jms Queue -> Route B -> WS call.
What I expect is that Route A and Route B have the same traceId, but what I get is 2 traces:
one for Route A -> Jms Queue, and another one from Jms Queue -> Route B.
See also the discussion in the link above for more info.