0

I am using Karma to test my node server. After about a minute of running there is a "failed to proxy" error with error code 'ENOBUFS'. The error happens in 'karma/lib/middleware/proxy.js'. I have read a similar issue here: Very simple Node.js client throws error ENOBUFS after many http requests

and some more background here: https://github.com/joyent/node/issues/3269

But I cannot find a workaround for my situation since the http requests are out of my control. Is there a way to work around this issue?

Community
  • 1
  • 1
Arwen Pond
  • 33
  • 1
  • 5
  • What platform is this? Have you established whether or not you're running out of ports? (Is this just a cosmetic issue? You don't actually need to support so many connections from the same source IP address, right? Or is this some application where all the connections are between the same two endpoints?) – David Schwartz Dec 20 '13 at 22:42
  • This happens on Windows 7, Windows 8 and Ubuntu. When I run 'netstat -nt' I see hundreds of sockets in 'TIME_WAIT' status. – Arwen Pond Jan 06 '14 at 22:26
  • Is there an actual problem or is this just a cosmetic issue? – David Schwartz Jan 06 '14 at 22:27
  • There is an actual problem. The tests fail because the server becomes unresponsive. – Arwen Pond Jan 07 '14 at 19:00
  • When the server is unresponsive, it is out of ephemeral ports? (Look at the `netstat` output.) – David Schwartz Jan 07 '14 at 20:50

0 Answers0