EADDRINUSE error on Service Bus requests

[martinza78]

We're putting some load through a node app on Azure using the sdk for service bus. We're getting the following error when putting messages onto, receiving them from , deleting and unlocking them. This error only happens directly on a call to service bus.

To make it worse the error is intermittent and only when we start loading the requests. If we take out the service bus there isn't a problem.

{"stack":"Error: connect EADDRINUSE\n at errnoException (net.js:904:11)\n at Object.afterConnect as oncomplete","message":"connect EADDRINUSE","code":"EADDRINUSE","errno":"EADDRINUSE","syscall":"connect"}

#1290

[martinza78]

Any feedback?

[dbuentello]

same here. im getting this on both sides (sending and receiving)

[markusahlstrand]

Also had similar issues. Could this be as mentioned in this blog post (http://blog.gluwer.com/2014/03/story-of-eaddrinuse-and-econnreset-errors/) that we're running out of ports as the ports get closed and stuck in TIME_WAIT? Haven't found any good source of information about how this actually work, but as far as I understand the default agent closes the connection if there isn't any connections queued up meaning we could use up the available sockets quite quickly if we have some traffic.
One possible solution might be using an Agent which keeps the connections open (such as keep-alive-agent), but so far I haven't found a way to use this without editing the code in the npm package. Any additional information on this is much appreciated.

/Markus

[amarzavery]

Closing this issue due to age.