Hello Alex,
thank you for your feedback. Okay, so now I totally assume that the error is on my end.
I checked the compability matrix you provided aswell as the libraries which are in use.
For the components I have:
Broker#1 is version 10.2.1.32 Broker#2 is version 10.2.1.32 OpenTelemtry Collector is otel/opentelemetry-collector-contrib :0.68.0 PubSub+ Messaging API for JMS - I am using the sdkperf from GA10.17 PubSub+ OpenTelemetry Integration for Solace JMS API: I am using version 1.0 OpenTelemetry Instrumentation for Java: I am using version 1.19.0 > I also compared the freshly downloaded md5 sums from the maven with the libs provided in the sdkperf and they are the same. The first md5sum is the one downloaded from maven, the second one (with lib/) is the one coming with sdkperf.
filip@SIT-:~/solace-sdkperf-jms/send$ cat opentelemetry-instrumentation-api-1.19.0.jar | md5sum
c5c8c6c8a769f73b8eeabc7e4a16469b -
filip@SIT-:~/solace-sdkperf-jms/send$ cat lib/opentelemetry-instrumentation-api-1.19.0.jar | md5sum
c5c8c6c8a769f73b8eeabc7e4a16469b -
filip@SIT-:~/solace-sdkperf-jms/send$ cat solace-opentelemetry-jms-integration-1.0.0.jar | md5sum
508b616474f74d4b3469c93599cbd28f -
filip@SIT-:~/solace-sdkperf-jms/send$ cat lib/solace-opentelemetry-jms-integration-1.0.0.jar | md5sum
508b616474f74d4b3469c93599cbd28f -
The only - main difference - I can currently see would be that I am using sdkperf and you are using a custom java programm
com.solace.samples.dt.jms.example.TimeEventPublisher
I sadly do not have access to the distributed tracing EA version. Maybe can you check your example with sdkperf if it still works as expected ? Or you can somehow provide me your example setup so I can test it with my Broker setup to see if that makes any difference.
Greetings,
Jan-Filip