Home > other >  Tcp server detected connection broken, collapse drops is how to determine the end, or intermediate r
Tcp server detected connection broken, collapse drops is how to determine the end, or intermediate r

Time:12-01

So-and-so cloud room transnational network adjustment, a few days ago have broken network operation, our server can detect network disconnection,, (recv returns 1, error code WSAECONNRESET, without a heartbeat package)

According to my understanding, the TCP connection disconnected in the middle of the network, server and the client should be undetectable!


It is embarrassing that we are IM services, IM away network need to decide the server detected is intermediate network disconnect (wanted to judge by application layer heartbeat package), or the client side (IM agent node) collapse,

Intermediate network disconnection: IM server user information from IM agent node will not delete immediately, waiting for the reconnection, IM agent node and connection proxy nodes in IM users will not be perceived network disconnection,

IM agent node collapse: IM server will remove the agent node information, at the same time connect users on IM agent node will be perceived,

CodePudding user response:

This thing just like where the cable pull, the client to pull in the middle node drawing is the same, unless the middle network disconnect first notify you,

CodePudding user response:

Why don't you notice? TCP handshake will send a RST give you four times, unless it is to not to close the client side, straight line or similar operation,