I completely randomly found this thread while looking to debug a separate issue, but this is a little-brought-up, but well-known issue with Windows on EC2. It looks like Amazon found the root cause and corrected it. Is there any way to forcefully close all these TIME_WAIT connections without restarting windows OS?Īfter few days we app stops taking any new connections. What could be the reasons behind this situation? HKEY_LOCAL_MACHINE\System \CurrentControlSet\Services\Tcpip\Parameters does not have TcpTimedWaitDelay key, so value should be the default (2*MSL, 4 mins)Įven if there are thousands of connection requests are coming at the same time, why windows OS is not able to clean them eventually? These connections don't seem to close even after stopping web server (waited 24 hours) ![]() There are around 69,250 (http port 80) 15000 (other than port 80) TCP connections in TIME_WAIT state (used netstat
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |