Q. When I enable javaagent debug mode, I get a "io.opentelemetry.extension.trace.propagation.B3 Propagator ExtractorMultipleHeades - Invalid TraceId in B3 header:null, Returning INVALID span context" log.

[eottabom]

It is used as a combination of armeria and spring,
Enable and use option to change REST request to gRPC in armeria.
This problem occurs when you enable the otel java agent debug log,
io.opentelemetry.extension.trace.propagation.B3 Propagator ExtractorMultipleHeades - Invalid TraceId in B3 header:null, Returning INVALID span context
Is there a phenomenon like memory leak in this case?

[laurit]

Is there a phenomenon like memory leak in this case?

No.
This message is logged at https://github.com/open-telemetry/opentelemetry-java/blob/0750660f6f0ab4130b81647921b21dafd48cf417/extensions/trace-propagators/src/main/java/io/opentelemetry/extension/trace/propagation/B3PropagatorExtractorMultipleHeaders.java#L38 It is just an informative statement, it does not indicate that anything is wrong. It is logged for example when the request doesn't have b3 propagation headers.

[eottabom]

I don't know if it's that influence, but I don't think traceid collection is possible.

[laurit]

I don't know if it's that influence, but I don't think traceid collection is possible.

I have no idea what you mean by this.

[eottabom]

Sorry.
I understand disabling the log, but it seems to happen because the trace id is not in the header. So, I'm trying to tell you that it's hard to trace with the trace id.

[laurit]

I'm still not sure what the question is here. We can't do anything about the trace id not being present in the header. If you want context propagation to happen then you'll have to configure the system that sends the request to add appropriate context propagation headers.

[eottabom]

When the intention of the question was grpc, there was such a problem, so I left an inquiry. Thank you for your answer. Let me check the cause further.

I'm sorry for the confusion.