Basically you're saying to set TCP: keep-alive in both client AND server? How can I do that? Moreover, after setting it to keep-alive, shouldn't I set some kind of timeout in the server too? Or is it just something fired by the client when no response is received? Thanks
On Mar 30, 4:05 pm, Ben Noordhuis <[email protected]> wrote: > On Fri, Mar 30, 2012 at 15:31, Masiar <[email protected]> wrote: > > Ok, I removed the callback. I don't understand what's `NODE_DEBUG="net > > http" node script.js` and how to use it, but I've discovered why the > > server was not responding. > > Now the communication is happening, but still even if I put a > > SOCKET_TIMEOUT of 1000000 (1000 seconds, 16 minutes more or less) > > after 8 minutes I start getting errors like "problem with request: > > socket hang up" (from the println in the request) and "problem with > > request: connect ETIMEDOUT". Any clue on what's going on? > > Probably that the other end of the connection (i.e. the server) is > setting a timeout of its own. As the saying goes, it takes two to > tango. You (as in: your client and the server) may also have to enable > TCP keep-alive. -- 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
