Many different requests with a same traceId, seems a bug?

[lmssy]

I have a server which receive http request, I use auto instrument to log trace and span and save them in elasticsearch.

Today I check my elasticsearch and found many requests this server received have a same traceId, and these requests come from quite a different time, for example today and yesterday.

As you can see below there is 1080949 requests with same traceId.

instrument version:
io.opentelemetry.javaagent.jetty-8.0, 1.2.0-SNAPSHOT

BTW, where can I found the source code of generating this traceId?

[mateuszrzeszutek]

It's in the IdGenerator class.

Are you certain that this traceId wasn't propagated through the request headers? All those SERVER spans all root spans of their respective traces, or do they have parents?

[jkwatson]

could the traces be being initiated by an android client using an old version of otel with a bad IdGenerator implementation?

[lmssy]

Now I update javaagent to 1.4.1 but problem still there, as you can see below one trace "00ac14092616288451054246389d0001" have 30000+ spans:

All those spans have they parentSpanId, but there is not any parentSpanId can be found as a spanId in this trace, this mean spans are isolated to each other with a same traceId.

All spans are SPAN_KIND_SERVER come from an http api provided by my springboot application, clients are outside applications which have no instrument, so my server is the first jump.

So why tihs siutation happens?

BTW, I have tried to search from the source code to find out when a traceId and spanId is created and set into context, but cannot find any code in opentelemetry-java-instrumentation using RandomIdGenerator to do this

[mateuszrzeszutek]

Is it perhaps connected with the Jetty Continuation issue from this thread: #3904?

[lmssy]

Actually I have tested by send many requests concurrently to a server with Jetty Continuation, and the traceId&spanId looks good, no above problem.
So I'm doing further investigation without any clue.

[muneeb-dar]

Was this issue resolved. I am using istio gateway and for kafka requests I am facing simila issue?

[kyouSS]

I ran into this issue as well.
In my case, the problem was that I never closed the scope of span.makeCurrent(). If you are using Span.makeCurrent(), make sure to close the scope by putting that in an try-with-resource statement, or manually close the scope in a finally block.

[Mityushin]

I encountered a similar situation, for a long time I could not find the reason for the "sticking" of trace_id. Your comment helped me find a similar error in the code. Thank you