The Dubbo plugin may have a broken trace problem

[steverao]

Describe the bug

About Dubbo instrumentation, from our customers, we found it will return expected result:

opentelemetry-java-instrumentation/instrumentation/apache-dubbo-2.7/library-autoconfigure/src/main/java/io/opentelemetry/instrumentation/apachedubbo/v2_7/TracingFilter.java

Line 43 in 02efad2

boolean isServer = rpcContext.isProviderSide();

In provider side, it might returns false and causes broken trace with upstream client's trace.
But I can't reproduce it in my local environment, it might causes by several factors.
From our customers' use cases, it will happens in Dubbo 2.7.10. I also talked with maintainer @AlbumenJ from Dubbo community. He expressed we shouldn't use it continuously and he doesn't recommend using it to check the source.
I also noticed there are some related issues in Dubbo community. For detail, please refer to https://github.com/apache/dubbo/issues?q=is%3Aissue+rpccontext+isconsumerside+is%3Aclosed

Steps to reproduce

But I can't reproduce it in my local environment, it might causes by several factors. I found it by our customers.

Expected behavior

The Dubbo instrumentation should produce correct trace.

Actual behavior

In some scenarios, it will produces broken trace due to wrong return of rpcContext.isProviderSide()

Javaagent or library instrumentation version

2.10.0

Environment

JDK: JDK8
OS: CentOS

Additional context

No response