I have an RMI process running on 5 Unix boxes and they work successfully with no problems. However on another box I start the process, it polls the port for about ten seconds (I have seen this using truss) then gives up. The code is exactly the same as the other boxes however, obviously there will be configuration differences to the other boxes. This is a solaris 8 box running JDK 1.4.1_05-b01. If anyone �ANYONE� knows what could be wrong then please let me know.
My trusted infrastructure team thinks the patches may not be up-to-date. Any help will be greatly appreciated.
posted 12 years ago
Hi Cameron, I have experiences at least a similar problem. The reason was the 'rmiregistry' in my usr/sbin directory, whisch was started by default. That one was listening to second port, allthoug it was set to the standard port 1099. I fixed this probelem, using the 'RMIREISTRY' FROM MY oracle installation, whish is listenin correctly only to the given port.
Screaming fools! It's nothing more than a tiny ad:
the new thread boost feature brings a LOT of attention to your favorite threads