-
Notifications
You must be signed in to change notification settings - Fork 1
ErrorsOnClientSide
- Connection timeout
- Socket timeout
- Keep Alive time
-
A connection timeout occurs only upon starting the TCP connection. This usually happens if the remote machine does not answer. This means that the server has been shut down, you used the wrong IP/DNS name, wrong port or the network connection to the server is down. if the TCP connection has been established before the server is overloaded you will get a socket exception
-
A socket timeout is dedicated to monitor the continuous incoming data flow. If the data flow is interrupted for the specified timeout the connection is regarded as stalled/broken. Of course this only works with connections where data is received all the time.
-
By setting socket timeout to 1 this would require that every millisecond new data is received (assuming that you read the data block wise and the block is large enough)!
-
if the TCP connection has been established before the server is overloaded you will get a socket exception else connection timeout occurs