TraceId spreading between containers thread pools

[CyberpunkPerson]

Hi Spring Team!
We found a bug with traceId spreading in TracingChannelInterceptor the issue starts in here, the essence of the bug here.

Best regards,
Andrew

[maecval]

@marcingrzejszczak
Hi Marcin,
Thanks for the fix.
Can you tell us what we can do to get this fix asap?
The bug causes major issues in our productive environment.
Is there a hotfix release available?
Cheers!
Valentin

[marcingrzejszczak]

You can either disable that integration via the spring.sleuth.messaging.enabled=false property, or wait until 17.02 when we do the release or use tools such as jitpack.io to point to a concrete commit in this repository and use a snapshot version.

[maecval]

Thanks for the quick response.
We have already disabled it for transactions (spring.sleuth.tx.enabled=false) and need to check what it means if we disable it for messaging.

[marcingrzejszczak]

This issue is about TracingChannelInterceptor which is a messaging component. If you disable messaging support in Sleuth then you won't have issues with TracingChannelInterceptor

[maecval]

As far as we understand we will loose the population of traceId / spanId if we do so we so.
BTW: it is certainly closely related to issues 2082 which is also one of the issues our apps suffer.

[marcingrzejszczak]

Yes, you will lose that functionality

[gigermocas]

Hi, can we expect this fix on a 3.0.x release?