### Current Behavior
TCP out node in listening mode not working properly, if …a client disconnects unexpectedly, it throws a socket error and some of the still active clients stop receiving data.
### Expected Behavior
1:Configure a tcp-out node in listen mode (in my example, write timestamp every 1 seconds)
2:Connect with multiple clients ( putty, telnet, localhost in my case, but i tested also from multiple external clients)
3:Kill a terminal from task manager or plug off the ethernet from a remote client
4:The rest of the clients still receiving the data
### Steps To Reproduce
1:Configure a tcp-out node in listen mode (in my example, write timestamp every 1 seconds)
2:Connect with multiple clients ( putty, telnet, localhost in my case, but i tested also from multiple external clients)
3:Kill a terminal from task manager or plug off the ethernet from a remote client
4:The node red console writes socket error, the other clients randomly stops receiving data
### Example flow
```json
[
{
"id": "69b8f80db494f181",
"type": "tcp out",
"z": "360d032be0511281",
"name": "",
"host": "",
"port": "50000",
"beserver": "server",
"base64": false,
"end": false,
"tls": "",
"x": 520,
"y": 120,
"wires": []
},
{
"id": "d8083637a25dd4a4",
"type": "trigger",
"z": "360d032be0511281",
"name": "",
"op1": "",
"op2": "0",
"op1type": "date",
"op2type": "str",
"duration": "-250",
"extend": false,
"overrideDelay": false,
"units": "ms",
"reset": "",
"bytopic": "all",
"topic": "topic",
"outputs": 1,
"x": 280,
"y": 120,
"wires": [
[
"69b8f80db494f181"
]
]
},
{
"id": "50c6bd3df2d0fe6e",
"type": "inject",
"z": "360d032be0511281",
"name": "",
"props": [
{
"p": "payload"
},
{
"p": "topic",
"vt": "str"
}
],
"repeat": "",
"crontab": "",
"once": false,
"onceDelay": 0.1,
"topic": "",
"payload": "",
"payloadType": "date",
"x": 140,
"y": 40,
"wires": [
[
"d8083637a25dd4a4"
]
]
}
]
```
### Environment
- Node-RED version:
- Node.js version:
- npm version:
- Platform/OS:
- Browser:
