why trace id bind with thread and it won't reset

[liu-junchi]

Java agent, version: 8.1.0

This trace link has been maintained for many days and has not ended

Then I find they have same thread, like 'DubboServerHandler-10.253.130.106:30013-thread-200', if this thread process request, the trace id is always same.

Why this happen, hope for help, thanks.

[wu-sheng]

It means you have faced some tracing context leak. The reason is uncertain, maybe some plugins don't match your cases.

[liu-junchi]

Could it be caused by asynchronous propagation?

[wu-sheng]

I am afraid mostly not. Async scenario usually causes trace breaking, rather than leaking.

[liu-junchi]

Not every time this request link will cause this result, it looks like it’s random, and it’s hard to find the reason. :(

[wu-sheng]

It could be random or thread reuse model. It is hard to determine from this general description.

[liu-junchi]

In most cases, random events may be related to multi-threaded scenarios, so I just guessed that it may be the reason for async scenario. Or there are some other multi-threaded scenarios.