I put Wireshark to both client and server, and captured something I cannot understand. This wrong behavior also cause client try to reset the connection and the original socket seems dropped. As you can see, everything is fine until the client sent However, another strange thing is: in server side, after 8-9 minutes it does send a Please help me to analysis what's going on during this process. It seems the client can reproduce this issue once 4-5 minutes when no communication between the two sides. Please ask me if more information needed. asked 03 Dec '15, 18:57 JerryBian edited 03 Dec '15, 19:00 |
One Answer:
It looks like the server has a TCP Keepalive timer of 10 minutes. This might be too long to stay in a firewall's connection table. "It seems the client can reproduce this issue once 4-5 minutes when no communication between the two sides." If this assumption is true then reducing the Keepalive interval at the server below 5 minutes should fix this... http://www.tldp.org/HOWTO/html_single/TCP-Keepalive-HOWTO/#preventingdisconnection Regards Matthias answered 04 Dec '15, 00:12 mrEEde |
What is between the client and the server? A piece of cable, LAN with several switches, the internet...?