While doing some intense thread testing, I generated the following exception with a multi-threaded client pounding on my server (only something like 60 threads):
java.rmi.ConnectException: Connection refused to host: 126.96.36.199; nested exception is: java.net.ConnectException: Connection refused: connect at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574) ...
Is this "normal"? That is, is this just an artifact of my testing or is there something fundamentally I'm missing in my RMI handling? Like is the RMI server just plain run out of connections/thread pool and may be something I can set to a higher value?
Vince<br />SCJP(1.4), SCWCD(1.4), SCJD (5.0)
Joined: Jan 12, 2007
OK, did a search and looks like this has been discussed before at: