Spans are not connected after upgrading spring-web-starter about java-spring-web HOT 3 OPEN

@lubinson Since you have already done an initial investigation and have an idea of how to fix the problem, care to create a PR for it?

Thanks

from java-spring-web.

hi @lubinson, what client/technology are you using to create request from service A to services B and C?

Ultimately would you be able to share a small reproducer?

from java-spring-web.

@pavolloffay

Thanks for your reply. After a deep looking, I found the Spring Webflux Webclient is auto injected with a filter TracingExchangeFilterFunction. This actually starts a new Tracing (Tracing 2 and Tracing 3) to Service B or Service C, which the tracing starts with span GET and POST. And I think this injection overwrote the tracing context we injected so the linked spans are broken.

After I removed the auto injected filter, everything is ok as before. I think this is a change of new version. Its better to make it configurable, especially for upgrading cases. And further, despite of my case, I am not sure this injection created span will connect spans before and after?

The reproducer is a little bit hard, because it is integrated with Spring Boot and other code. But the basic case is All Services are spring boot applications instrumented with Jaeger, Client call Service A, Service A processes its business and then uses auto injected WebClient.builder() (this Webclient is the one mentioned above) to call Service B and Service C. Then you will see the happening. Pls be note that Service A processing has multiple threads switching, we use some context to take the root tracing context and inject it to the HTTP header then use Webclient to call Service B and C.

Thanks.

from java-spring-web.