What if the Windows TCP connection waits for too much processing of the session

It is believed that many inexperienced people don't know what to do if the Windows TCP connection waits for too much session processing. Therefore, this article summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

Phenomenon:

There are as many as 16005 processes in time_wait under cmd, and they are all useless processes. If the waiting process is not dealt with in time and the waiting process continues to expand, it will cause the system resources to be exhausted and the system crashes.

Analysis:

The default TcpTimedWaitDelay parameter is set to 4minutes, which will be disconnected automatically once the process waits for more than 4 minutes. In view of the fact that there are so many waiting processes without in-depth analysis, in view of the invalid waiting connection, I will adjust the waiting timeout to 60s by changing the registry, so that the system can automatically handle the waiting timeout process.

Solution:

Modify the registry: new dword key TcpTimedWaitDelay under HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Services\ TCPIP\ Parameters, and set its value to 60

Restart the operating system

After reading the above, have you mastered how to handle too many Windows TCP connections waiting for sessions? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!