Questions tagged [time-wait]

The TIME_WAIT TCP port state

Indicates that both endpoints of a connection have closed it, and that the local end is keeping the local port in TIME_WAIT state. The system is waiting for any remaining packets to expire before closing the port. This state only lasts 2*MSL seconds where MSL is the maximum segment lifetime, typically 60 or 120 seconds.

The TIME_WAIT state is often erroneously regarded as a performance problem. It isn't, except for the length of netstat displays. However it can be avoided altogether by being the end which receives the first FIN. In practice this means the client should close the connection before the server, so that the ports in TIME_WAIT state accumulate at the client, where they are few, rather than at the server, where they are very many.

108 questions
-1
votes
3 answers

C# Webdriver code to wait

I have been all the day trying to make: Wait 10 seconds between two actions in webdriver Waiting long enough for the element to displayed (the id element) (because in Internet Explorer get the error "Unable to find element with id ==…
Lion6
  • 125
  • 1
  • 6
  • 16
-2
votes
3 answers

Why is the same socket in TIME_WAIT many times?

I have read other threads regarding sockets in TIME_WAIT, but I am clearly still missing something. Below is a few lines from a "netstat -an". How could it get into this situation? If I understood the descriptions I found, we should not have more…
R. Hartman
  • 129
  • 1
  • 5
-3
votes
1 answer

the random port initiates the TCP request

the random port initiates the TCP request between two server programs on centos 6.8. # netstat -an|grep 6001 tcp 0 0 0.0.0.0:6001 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:52470 …
borey
  • 5
  • 3
1 2 3 4 5 6 7
8