Jaeger Showing 2 Traces With Same MessageId

[carlyn12]

Describe the bug
I have two simple spring boot apps that communicate over jms and implement
opentelemetry auto tracing with jaeger. When sending the traces to my local jaeger instance, I see two different traces showing where one is correctly showing both spans end-to-end and the other appears to be a duplicate that has the same messageId as the consumer.

**UPDATE: this behavior is only occurring when I have Dotel.resource.attributes=service.name property set to the same thing in both the consumer and producer

To Reproduce
Steps to reproduce the behavior:

built both apps with maven
start jaeger-all-in-one docker container
run the applications with the following command:
-Dotel.metrics.exporter=none
-Dotel.exporter.jaeger.endpoint="http://localhost:14250"
-Dotel.resource.attributes=service.name="OTLJmsAuto"
-Dotel.traces.sampler="always_on"
-Dotel.instrumentation.jms.enabled=true
-Dapplication.home=./
-Dapplication.name=producer
-javaagent:./opentelemetry-javaagent-all.jar
-jar ./target/producer-0.0.1-SNAPSHOT.jar
navigate to http://localhost:16686/search and see two different traces showing(see screenshots)
Expected behavior
Only the top trace should show which includes two spans(producer and consumer).

Version (please complete the following information):

OS: Linux
Jaeger version: 1.22
What troubleshooting steps did you try?
Tried upgrading dependency versions as well as using the latest version of opentelemetry-javaagent-all.jar. Tried with debug mode.

[trask]

hi @carlyn12!

So, currently this is expected. There's a test that shows this same behavior that you describe:

https:/open-telemetry/opentelemetry-java-instrumentation/blob/main/instrumentation/jms-1.1/javaagent/src/jms2Test/groovy/SpringListenerJms2Test.groovy#L28-L36

We are not sure ourselves though what is the correct behavior here:

open-telemetry/opentelemetry-specification#1085

[trask]

Closing, this is now configurable using

-Dotel.instrumentation.messaging.experimental.receive-telemetry.enabled=false

to disable the receive span