[Bug] Dubbo 3.2.11 work with Istio get no provider, connection error

[wilsonwu]

Pre-check

• I am sure that all the content I provide is in English.

Search before asking

• I had searched in the issues and found no similar issues.

Apache Dubbo Component

Java SDK (apache/dubbo)

Dubbo Version

Dubbo 3.2.11

Steps to reproduce this issue

Use triple call provider api with istio sidecar injection, after about 1-2 hours, get RPC error, the log shows no provider problem.

By troubleshooting, we found the problem may be netty get the wrong connection status, the connection is health, but netty mark it as bad, so the RPC has been terminated.

What you expected to happen

Work fine as it start.

Anything else

No response

Are you willing to submit a pull request to fix on your own?

• Yes I am willing to submit a pull request on my own!

Code of Conduct

• I agree to follow this project's Code of Conduct

[chickenlj]

What's the service discovery mechanism that is used on the consumer side?

Is dubbo consumer SDK or sidecar responsible for subscribing addresses from registry?

[wilsonwu]

#13600 I have commented here, hope this can help, this is very difficult to describe, the way of integration like: https://dubbo.apache.org/zh-cn/overview/tasks/mesh/dubbo-mesh/

[liang2h]

is this problem solved？

[wilsonwu]

is this problem solved？

By downgrade Dubbo to 3.2.10, it is solved.

[liang2h]

is this problem solved？

By downgrade Dubbo to 3.2.10, it is solved.

Have you found the reason yet? What is wrong with 3.2.11

[wilsonwu]

is this problem solved？

By downgrade Dubbo to 3.2.10, it is solved.

Have you found the reason yet? What is wrong with 3.2.11

I think #13600 this is the reason, you can see my comment.