TCP Request Node Error not caught

[mlschuh]

Hello!

I'm going to preface this with the fact that I'm running a rather old version, 1.0.3, for mostly political reasons. It's a production system that's been in place for many years and budget to update it, no matter how safe it should be, doesn't really exist unless forced. With that said, this post is more of a "Has anyone seen this before and do we know if it specifically has been resolved since".

I have a flow that contains many TCP Request nodes. Last night, one of them threw a ECONNRESET, restarted the NR process in safe mode, and sat there. It was easy enough to re-deploy but this is the second time and I thought that NR should be catching all of these errors instead of it crashing the process.There's probably a dozen reasons why the connection could have been reset so I don't think a root-cause analysis would be fruitful. I also have no way of reliably reproducing it.

This specific node with this name appears in a few different places so I can't be sure of the exact one that failed but here's a (probably less than useful) view of one inside a subflow.

Environment
Docker on Ubuntu

Version
1.0.3

Has anyone seen this before? Or better yet, was this a known bug and resolved in the prior few years?

[Colin]

That does suggest a bug in the TCP node. Nodes should catch any errors and deal with them. If the node does not catch it then it is passed up to node-red which has no option other than to terminate. Anything else might be unsafe.

Most likely the bug was fixed a long time ago. If it does still exist then if reported now it would be fixed urgently, I am sure. You could trawl back through the node-red release notes to see if you can find it.