I've been going nuts trying to get my socket connections under control. Unlike most posts, where people are hitting the maxSockets limit and need to free it up, I have code connecting to a localhost server (couchdb) using http.
It appears that socket pooling is ignored, as well as maxSockets, when connecting to a resource on the same machine the node.js script is running on. As a result, after a while, I discover 3,000 + TCP connections to CouchDB when my node.js server is under load... eventually causing problems that require CouchDB be restarted. The same code, running on my local machine against the CouchDB server, creates/consumes 1 socket under a light load (hitting refresh in the browser). 1. Has anyone encountered this problem? 2. Does anyone have a solution? Thanks, Greg -- 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
