LI123456mo commented on issue #16558:
URL: https://github.com/apache/dubbo/issues/16558#issuecomment-6494793262

   Reproduced on 3.3.6 (Ubuntu VM, provider and consumer both `tri` on port 
50051, direct URL, no registry).
   
   Steps: connected a consumer, then blocked its packets with `iptables -A 
OUTPUT -p tcp --dport 50051 -j DROP` without closing the connection. After ~10 
minutes the server still listed the old connections as ESTABLISHED. `ss -tano` 
shows no keepalive timer on the server sockets, which fits the finding that 
SO_KEEPALIVE isn't set. After I removed the rule, the consumer opened a new 
connection on its own; `ss -tan` (screenshot below) shows the old connections 
(peer ports 38158 and 36590) with only a server-side row and no client-side 
counterpart, so they are orphaned.
   
   @EarthChen could you confirm whether `heartbeat.timeout` is meant to apply 
to the `tri` server? I haven't compared against the `dubbo` protocol yet.
   
   <img width="877" height="104" alt="Image" 
src="https://github.com/user-attachments/assets/4c5bb8d9-e0c3-49a6-b478-470a5b5d4613";
 />


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to