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 myTaskExecutor is not applicable to get wrapped via proxy. In Spring Cloud Sleuth we're doing our best so that all instrumentation gets done automatically, behind the scenes. In this case a user has to manually call Sleuth internals to wrap the ThreadPoolTaskExecutor in a tracing representation.
A related case has been reported in #21484... While there is not much we can do about that case of triggering hard references to other beans from an AsyncConfigurer class, we should be able to make your case here - Executor post-processing - possible through lazily accessing the executor as well as the exception handler. I'll see what we can do for 5.1 here.
Uh oh!
There was an error while loading. Please reload this page.
Marcin Grzejszczak opened SPR-17021 and commented
Having such code
The
myTaskExecutor
is not applicable to get wrapped via proxy. In Spring Cloud Sleuth we're doing our best so that all instrumentation gets done automatically, behind the scenes. In this case a user has to manually call Sleuth internals to wrap theThreadPoolTaskExecutor
in a tracing representation.Affects: 5.0.7
Reference URL: spring-cloud/spring-cloud-sleuth#1022
Issue Links:
Referenced from: commits f6fdffd
The text was updated successfully, but these errors were encountered: