We are trying to test the maximum socket/connection load on our brand new
Mac Pro.

I have set up on the Mac Pro server a basic server application that waits
for connections and receives them.

On the client end, I have a program that can generate any number of
clients I desire and make them all connect at whatever interval I choose
(this way they aren't trying to connect too quickly one after another).

I am running into the weirdest problem. The server can receive ROUGHLY 376
connections and then, despite the fact that netstat says the port is
listening on the server, no clients (on any computers) can connect. They
spit out a

java.net.ConnectException: Operation Timed Out

error.

I have plenty of memory and CPU left on the server when it stops
receiving connections, and I know it probably has nothing to do with a
maximum socket setting because sometimes it will allow 376, sometimes
more, and sometimes fewer connections... so it can't be a limit on the
number of threads/sockets etc.

I am racking my brain trying to figure this out... and what the heck does
it mean when an operation times out rather than the connection timing out?

Josh <><