>> >> So anybody know what resource "free ports" relates to in the unix >> domain socket case? Are there any other debug options to find out >> more about what is happening. > > I suspect the connect() call returns EAGAIN
Digging some more, it looks like the kernel returns EAGAIN when the
backlog on the other side is full (the backend doesn't accept() fast
enough).
Lukas
