RMI generally won’t work over a firewall, since it uses unpredictable ports (it starts off on 1099, and then runs off with a random port after that). In these situations, you generally need to resort to tunnelling RMI over HTTP, which is described well here.
Keep a strong reference to the object that implements the java.rmi.Remote interface so that it remains reachable, i.e. ineligible for garbage collection. Below is a short program that demonstrates a java.rmi.NoSuchObjectException. The script is self-contained, creating an RMI registry as well as a “client” and a “server” in a single JVM. Simply copy this code … Read more
This is item A.1 in the RMI FAQ. You need to either fix your /etc/hosts file or set the java.rmi.server.hostname property at the server.
The error message says it all: your connection timed out. This means your request did not get a response within some (default) timeframe. The reasons that no response was received is likely to be one of: a) The IP/domain or port is incorrect b) The IP/domain or port (i.e service) is down c) The IP/domain … Read more
Run the rmiregisrty command from your /bin, /build, or /build/classes folder, whichever folder is the root of your built files. I spent half a day trying to solve that same thing.
There are four cases of this exception. When exporting: you didn’t run ‘rmic’ and you didn’t take the steps described in the preamble to the Javadoc for UnicastRemoteObject to make it unnecessary. When binding: the Registry doesn’t have the stub or the remote interface or something they depend on on its classpath. when looking up: … Read more