Hi Chris,
That sounds like a lot of clients.
I also think the reason is too many clients. Because I ran the testcase over and over. The rmi server maybe have no time to run the Garbage Collector. I don't know about how many clients can connect to rmi server at the same time.
Are you trying to run them all at the same time?
Yes. I modified my testcase to created 2000 rmi clients. The process of creating these clients did not throw any exception. But after I called the 2000 threads to start, then connect exceptions were throwed in the running process of some threads, not all threads.
What OS is your server running on?
My server ran on Win2000 professional OS.
Any chance you are getting bounced because you are trying to open too many connections? Even if you stop your program and then restart, do you somehow disconnect gracefully, or do you leave the server hanging thinking you are still there? I don't know how all that is handled, but with massive amounts of clients, I could see something like that happening if the server never knew anyone was dropping out and you just kept adding more connections. Does it work again if you restart the server and then reconnect your clients?
Maybe, the rmi server needs more memory. I restart the server after connect exceptions were throwed, then I ran the testcase. Connect exceptions was also throwed in the running process of some threads. But, if I ran my gui client, gui client worked well and no problem. I don't know why rmi server canot response to some clients when so many clients called rmi method simultaneously.
Best Regards,
Light