Does a TCP Socket Connection Have a "Keep Alive"?
Unlike HTTP keep-alives, TCP socket connections do not remain open indefinitely. Instead, they are subject to a timeout limit enforced by TCP Keep-Alive.
Introduction
TCP connections involve two sockets, each residing on one end of the connection. Normally, these sockets remain open until one end terminates the connection, indicated by an FIN packet. However, if unintended socket termination occurs, TCP Keep-Alive exists to detect and close stale connections.
Keep-Alive Process
On Linux systems, TCP Keep-Alive operates with the following default settings:
If a connection remains idle for over tcp_keepalive_time, an ACK packet is sent to the other end. If there is no response after a specified number of probes, the connection is terminated via RST.
Gotchas
2 Hour Default: By default, the Keep-Alive process only initiates after 2 hours of inactivity, which may allow stale connections to persist.
Keep-Alive is Optional: Responding to Keep-Alive packets is optional, and some implementations may drop them.
Changing TCP Timeouts
To modify TCP timeouts, refer to the following OS-specific instructions:
Linux:
Mac OS X:
Windows:
The above is the detailed content of How Does TCP Keep-Alive Work and How Long Do Socket Connections Remain Open?. For more information, please follow other related articles on the PHP Chinese website!