Port limitations with many EJB Clients?

[rboston]

I've got an ejb app using 3.0 that has several hundred simultaneous stateful session bean clients.
Each of them are pumping data packets into the server at one second intervals and the server seems not to be able to handle it. By that I mean that it appears to be blocking on i/o. The server's cpu is fine, the client's cpu is fine but the data is not going through.
One possibility thought of was overloading the server port.
It looks like EVERY socket connection from the client is binding to 9444 on the server. (We change from the default.)
Is it possible that the port is overloaded with too much data?

If so, is there a way to have the ejb/rmi function like regular rmi where it creates a second connection between two different ports after accepting on the listening one?

Thanks

[jwoolsey]

Unless there is a bug with the TCP/IP implementation you can't overload a port. You may be able to tweak some configurations with the stack to improve performance under load.

Make a simple page that had some static data on it and flood the server. See if you have a speed problem with the infrastructure layers.