Your original error looks to be thrown **before** the HTTP client attaches it's error listener.
This is kind of insane because as soon as a socket is created it is assigned using ClientRequest.onSocket() and in a nextTick() handler it adds the error listener. The socket's nextTick() handler for this error is added before the nextTick() handler ClientRequest has BUT we shouldn't be getting network errors without a full cycle through the event loop. Has something changed in libuv that would allow us to get an ECONNREFUSED event before nextTick() handlers fire when the object is created? The "random disconnects" is another issue, if it is as issue at all. Node will disconnect sockets to the remote server when they are not in use. If this happens cleanly between HTTP requests there will be no error. -Mikeal On Feb 22, 2012, at February 22, 20128:01 AM, Rambo wrote: > I'm also experiencing random disconnects without any emitted errors, that's > just bizarre. I'm sure the server is not causing the disconnection. What > could be happening? > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
