Home >Java >javaTutorial >Here are a few question-based article titles that capture the essence of your content: **Focusing on the Main Point:** * **Do TCP Socket Connections Last Forever? Exploring Keep-Alive Timeouts** *

Here are a few question-based article titles that capture the essence of your content: **Focusing on the Main Point:** * **Do TCP Socket Connections Last Forever? Exploring Keep-Alive Timeouts** *

Susan Sarandon
Susan SarandonOriginal
2024-10-26 00:20:28700browse

Here are a few question-based article titles that capture the essence of your content:

**Focusing on the Main Point:**

* **Do TCP Socket Connections Last Forever? Exploring Keep-Alive Timeouts** 
* **How Long Do TCP Socket Connections Stay Open? Decodin

TCP Socket Connections and Keep-Alive

The concept of TCP Keep-Alive is often associated with HTTP, but it also applies to standard TCP socket connections. Unlike HTTP Keep-Alive, which allows a persistent connection for multiple requests, TCP Keep-Alive serves a different purpose.

Does a TCP Socket Connection Automatically Remain Open Forever?

No, a TCP socket connection does not automatically remain open indefinitely. There is a mechanism called TCP Keep-Alive that enforces a timeout.

TCP Keep-Alive Process

TCP Keep-Alive operates on three configurable parameters:

  • tcp_keepalive_time: Default 7200 seconds (2 hours)
  • tcp_keepalive_probes: Default 9
  • tcp_keepalive_intvl: Default 75 seconds

If there is no activity on a TCP connection for the specified tcp_keepalive_time, the system will send a Keep-Alive packet (an empty ACK). If the server responds with an ACK, the process resets. If no response is received after the specified number of tcp_keepalive_probes (with the tcp_keepalive_intvl interval between probes), the connection is terminated with a RST.

Gotchas

  • 2-Hour Default: The default 2-hour timeout can lead to stale connections lingering for extended periods.
  • Keep-Alive is Optional: According to RFC 1122, responding to or relaying TCP Keep-Alive packets is optional for systems. This means servers may not always honor the timeout settings. In practice, however, Keep-Alive packets are generally transmitted.

Changing TCP Timeouts

TCP timeout settings can be modified on the operating system level. However, this will affect all TCP connections on the system.

Linux

Use the following commands to change the settings for all connections:

  • tcp_keepalive_time: sysctl -w net.ipv4.tcp_keepalive_time=180
  • tcp_keepalive_probes: sysctl -w net.ipv4.tcp_keepalive_probes=3
  • tcp_keepalive_intvl: sysctl -w net.ipv4.tcp_keepalive_intvl=10

Mac OS X

Use sysctl to view and modify settings:

  • sysctl net.inet.tcp | grep -E "keepidle|keepintvl|keepcnt"
  • sysctl -w net.inet.tcp.keepidle=180000 net.inet.tcp.keepcnt=3 net.inet.tcp.keepintvl=10000

Windows

TCP Keep-Alive settings can be found in the registry:

  • HKEY_LOCAL_MACHINESystemCurrentControlSetServicesTCPIPParameters

The above is the detailed content of Here are a few question-based article titles that capture the essence of your content: **Focusing on the Main Point:** * **Do TCP Socket Connections Last Forever? Exploring Keep-Alive Timeouts** *. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn