You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Since release v1.10.0 the context propagation of a reactor-core context within spring cloud gateway is broken. I would only expect one trace for my sample scenario, but since v.1.10.0 two traces are produced.
Steps to reproduce
In a controller for spring cloud gateway I use a flatMap operation to chain two web service calls.
Simplified sample code in gateway controller:
What did you expect to see?
For agents until version 1.9.2 in jaeger I observe one trace for the whole operation. Simplified structure:
unknown_service:java /controller/backendmap
unknown_service:java ApiGatewayController.backendmap
unknown_service:java HTTP GET
unknown_service:java /controller/pojo
unknown_service:java ApiGatewayController.getPojo
unknown_service:java HTTP GET
unknown_service:java /controller/mojo
unknown_service:java ApiGatewayController.getMojo
What did you see instead?
With the new agent version 1.10.0 this trace is split up in two. It seems the context propagation in operation flatMap does not work anymore
Describe the bug
Since release
v1.10.0
the context propagation of a reactor-core context within spring cloud gateway is broken. I would only expect one trace for my sample scenario, but since v.1.10.0 two traces are produced.Steps to reproduce
In a controller for spring cloud gateway I use a
flatMap
operation to chain two web service calls.Simplified sample code in gateway controller:
full reproducer in https://github.com/dynatrace-peterlang/springapigateway-reproducer
What did you expect to see?
For agents until version 1.9.2 in jaeger I observe one trace for the whole operation. Simplified structure:
What did you see instead?
With the new agent version
1.10.0
this trace is split up in two. It seems the context propagation in operationflatMap
does not work anymoreand a second trace
What version are you using?
broken since
v1.10.0
Environment
Compiler: Eclipse Temurin 11
OpenJDK Runtime Environment Temurin-11.0.13+8 (build 11.0.13+8)
OS: Windows
Additional context
It seems context propagation was broken by changes in #4786
The text was updated successfully, but these errors were encountered: