GitHub user tommy-ham created a discussion: [Q/A][Java DUBBO RPC Triple (HTTP2)] How to close the zombi connection on the Provider side
### Pre-check - [X] I am sure that all the content I provide is in English. ### Apache Dubbo Component Java SDK (apache/dubbo) ### Details Environment: Dubbo 3.3.6, Triple protocol (HTTP/2) Issue: After a network partition, the Consumer-side socket is closed, but the Provider-side connection remains in the ESTABLISHED state (a zombie / half-open connection). Root Cause: Dubbo's Triple (HTTP/2) transport does not ship with any built-in connection liveness mechanism — neither TCP Keep-Alive tuning, HTTP/2 PING frames, nor an IdleStateHandler is configured by default. As a result, the Provider is unaware that the peer is gone, and the stale channel persists until the OS-level TCP keepalive (default: 2 hours on Linux) finally times out. Question: What is the recommended approach to detect and close these zombie connections on the Provider side? Specifically, is there a Dubbo-level configuration, a Filter/Extension hook, or a Netty pipeline customization point that allows us to inject PING-based or idle-based connection reaping? ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) GitHub link: https://github.com/apache/dubbo/discussions/16557 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
