Hi Jan-Filip,
I have tested a similiar setup and Stack IT Argus Service as observability tool.
I am getting the expected end-to-end trace from publisher to consumer:
My assumption is that the context propagation integration of the Solace JMS API does not work in your case, because you get different trace ids for clients and Solace event brokers.
I have not tested to use a connection factory, but I think this should not make any difference. Your commands look good so far.
That are my commands that I use for the publisher for example:
java -cp dt-sol-jms-example-1.0.0-SNAPSHOT-jar-with-dependencies.jar
-javaagent:`pwd`/1.19.0/opentelemetry-javaagent.jar -Dotel.javaagent.extensions=`pwd`/solace-opentelemetry-jms-integration-1.0.0.jar -Dotel.traces.exporter=otlp -Dotel.metrics.exporter=none -Dotel.instrumentation.jms.enabled=true -Dotel.javaagent.debug=false -Dotel.propagators=solace_jms_tracecontext -Dotel.resource.attributes=service.name=time_event_publisher -Dotel.exporter.otlp.endpoint=http://192.168.100.140:4317 -Dotel.bsp.schedule.delay=500 -Dotel.bsp.max.queuesize=1000 -Dotel.bsp.max.export.batch.size=5 -Dotel.bsp.export.timeout=10000 com.solace.samples.dt.jms.example.TimeEventPublisher <HOST>:55555 <user>@<vpn> <password>
This looks also similiar to your ARGS. I assume it is more a version compatibility issue.
Can you make sure that you follow the following compatibility matrix?
Distributed Tracing Version Compatibility
I am using this integration for Solace JMS API:
https://mvnrepository.com/artifact/com.solace/solace-opentelemetry-jms-integration/1.0.0
And I am using Solace JMS API in version 10.17 with the collector version that is part of the distributed tracing EA version.
Can you check your versions of those components and give feedback?
Thanks,
Alexander