4

I've set up a node web server which queries several webservices at every incoming request (via http.get). When the request return the web server will return the aggregated content to the user (coordinated by async).

Currently I'm doing about 10concurrenting requests to 8 different webservices that are as well located on the same machine. (it's a test setup)

Everything works fine when triggering the setup from the browser, but when I'm using ab to put a little load on the system (ab -n 1500 -c 42 127.0.0.1:31330/) after a short while I keep getting ENOBUFS errors.

I found very little on the internet regarding this issue. Does it have to do with the fact that the connection pool of my operating system simply overloads and thus is not able to perform any more requests as well as accept any new connections? Or is it simply a windows issue that will not appear on any other unix like system? (I'm using Win 7 x64) If it has to do with connections, does this issue exist on any operating system whatever technology (node.js, python, php etc.) is used?

Update: It appears that indeed some kind of connection pool is filling up, when I got that error from node at the same time accessing any other webpage is not possible anymore.

Is there anything that can be done here?

BenMorel
  • 34,448
  • 50
  • 182
  • 322
zaphod1984
  • 836
  • 2
  • 7
  • 22
  • From `man errno`: `ENOBUFS No buffer space available (POSIX.1 (XSI STREAMS option))` – Linus Thiel May 09 '12 at 10:02
  • yes but I'm running the script on windows 7 x64 – zaphod1984 May 10 '12 at 05:46
  • I am having the same problem. Did you learn any more about avoiding this problem? – Tom May 15 '12 at 14:56
  • Hi, i found this page: http://itamarst.org/writings/win32sockets.html According to it the enobufs problem occurs because of the limited buffer size in windows. (see the very last paragraph) I'm not totally sure if switching to linux will solve the problem, but I did not experience this problem on a linux machine. as i'm not really sure i did not post this as a answer because i did not want do mislead anyone. also the thing with not being able to open any internetpage anymore looks consistent to the buffer issue on windows. – zaphod1984 May 15 '12 at 15:32
  • @zaphod1984 do you still experience this with nodejs 0.10 ? – Benjamin Gruenbaum May 06 '13 at 12:21
  • I've not tested it recently but it looks like it is not a node issue but relates to the fact that I'm on windows. the problem did not occur when i tested on linux. – zaphod1984 May 07 '13 at 06:26
  • Any insights? I've got the same error. – Andras Hatvani Sep 09 '15 at 12:34

0 Answers0