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
The WebClientSenderConfiguration contains the auto-configuration for the WebClient based Zipkin sender. The RestTemplate based one honors the timeouts from the ZipkinProperties, while the WebClient based one does not. Unfortunately there is no client agnostic way to set the timeouts (the PR set the timeouts via a ReactorHttpClient, which ties the implementation to Netty).
Investigate if we can make this happen nonetheless, or at least document that the timeouts aren't honored with the WebClient one. Maybe we can use the timeout methods from Reactor somehow to workaround.
The text was updated successfully, but these errors were encountered:
Unfortunately there's no good way to configure connect and read timeout
separately, which works for all supported reactive clients. This
implementation applies a timeout through Reactor's timeout method. The
timeout from the properties is summed together and this is the applied
timeout. While not perfect, this is better than no timeout at all.
Closesspring-projectsgh-31496
The
WebClientSenderConfiguration
contains the auto-configuration for theWebClient
based Zipkin sender. TheRestTemplate
based one honors the timeouts from theZipkinProperties
, while theWebClient
based one does not. Unfortunately there is no client agnostic way to set the timeouts (the PR set the timeouts via aReactorHttpClient
, which ties the implementation to Netty).Investigate if we can make this happen nonetheless, or at least document that the timeouts aren't honored with the
WebClient
one. Maybe we can use thetimeout
methods from Reactor somehow to workaround.The text was updated successfully, but these errors were encountered: