I connect to socket server in NodeJs using this command:
client = net.createConnection()
How can I then properly disconnect from the server?
I tried client.end() and even client.destroy()
but when I check the connection status using netstat it shows that the connection is in state FIN_WAIT2.
How can I close and destroy the connection altogether?
This is the default TCP connection termination sequence,
By calling client.end() the node js will send the FIN packet to the server, and the server will response with a FIN packet to the client to accept the socket termination.
As of nodejs documentation what socket.end does is,
Half-closes the socket. i.e., it sends a FIN packet. It is possible the server will still send some data.
When the FIN packet is received the connection to the server from client is closed automatically and the socket.on('close', .. ) is fired and the ACK is sent back.
So the connection is terminated by agreeing both server and client so the server is able to send data that may require before closing the connection.
But when calling socket.destroy, the client connection will be destroyed without receiving the FIN packet forcefully. It is a best practice to avoid calling socket.destroy if possible.
Reference:
net.createConnection() returns a Socket object. client.destroy() is what you want to do.
Source: http://nodejs.org/docs/latest/api/net.html#socket.destroy
end() only closes the writing stream of the socket, the remote host can keep his writing stream open and send you data
socket.close = function(data) { var Self = this; if (data) this.write(data, function(){ Self.destroy(); }); else this.destroy(); };
client.end or client.destroySoon, which internally calls client.end.I have nodejs version 11.15.0 installed under GNU/Linux; the only way to disconnect a telnet-like client in this configuration is to call
socket.destroy()
Other methods on socket simply do not exist any more (eg: close() or disconnect()); also emitting close or end events does not work.
end() would require the other end to react which in my case it doesn't...
client.close()?