In monitoring the socket server on my local workstation, i notice that despite the logging always showing only 1 socket in use, netstat reveals it quickly maxes out at 5 socket ESTABLISHED connections to the backend server (sometimes 6). This is odd because when i originally investigated this on the actual server itself, i saw absolutely no TCP sockets open (not even CLOSE_WAIT).
But nonetheless, setting globalAgent's maxSocket to 10000 does allow the process to open heck a lot more connections to the backend. My colleagues have been using the socket server for the past week without re-occurrence of the problem. Much thanks, Aaron On Mon, Dec 31, 2012 at 4:15 PM, Aaron Seet <[email protected]> wrote: > Btw if I open up multiple tab windows and load up our web app + unit test > pages to form say four separate clients, and have them continuously hit the > socket server with data messages that require backend HTTP requests, I seem > to able to rather quickly (in terms of less than an hour) cause the Node > process to quit making new backend TCP connections. > > All these while the globalAgent's report is 1 socket and 0-1 requests, > which doesn't seem like some socket leak. Also between testing the x86 and > x64 versions, the memory consumption at point of stalling is approximately > 13MB and 25MB respectively. > > Wonder what else would cause ClientRequests to stop making connections > without error? > > > thanks, > Aaron > -- 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
