We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
Please consider adding error listener/emitter on TCP sockets. Right now I'm getting errors like below:
2015-06-30_16:14:17.57533 events.js:85 2015-06-30_16:14:17.57541 throw er; // Unhandled 'error' event 2015-06-30_16:14:17.57542 ^ 2015-06-30_16:14:17.57544 Error: connect ETIMEDOUT 2015-06-30_16:14:17.57545 at exports._errnoException (util.js:746:11) 2015-06-30_16:14:17.57546 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1010:19)
As a quick workaround I monkey-patched TCPSocket:
var native_dns_utils = require('native-dns/lib/utils'); native_dns_utils.TCPSocket.prototype._monkey_catchMessages = native_dns_utils.TCPSocket.prototype.catchMessages; native_dns_utils.TCPSocket.prototype.catchMessages = function () { var self = this; this._socket.on('error', function(err) { self.bound = false; self.emit('close', err); }); this._monkey_catchMessages(); };
Kind Regards, Rafal Kupka
The text was updated successfully, but these errors were encountered:
I just got stung by this. Causes hard to debug crashes of the entire application. Not cool.
Sorry, something went wrong.
Hit the same issue, looks like this module is not maintained anymore.
Add tcp socket error handler to fix tjfontaine#97
4068917
No branches or pull requests
Hi,
Please consider adding error listener/emitter on TCP sockets. Right now I'm getting errors like below:
As a quick workaround I monkey-patched TCPSocket:
Kind Regards,
Rafal Kupka
The text was updated successfully, but these errors were encountered: