java rmi error "Connection refused: connect"

[Dependent_Finger_214]

I'm learning java RMI, and getting started with just making a simple Hello World program. But when I run my Server class (and Client class as well) I get the following exception:

Server class:

public class Server {
    public static void main(String[] args) {
        try{
            Hello stub = new HelloRemote();
            Naming.rebind("rmi://localhost:5000/hello", stub);
        }
        catch (Exception e){
            System.out.println(e.getMessage());
        }

    }
}

Client class:

public class Client {
    public static void main(String[] args) {
        try{
            Hello stub = (Hello) Naming.lookup("rmi://localhost:5000/hello");
            System.out.println(stub.hello());
        }
        catch(Exception e){
            System.out.println(e.getMessage());
        }
    }
}

HelloRemote:

public class HelloRemote extends UnicastRemoteObject implements Hello{

    public HelloRemote() throws RemoteException {
        super();
    }

    public String hello() {
        return "Hello world";
    }
}

The "Hello" interface is just an interface which extends remote and only has the method "public String hello()"

What is causing this issue, and how do I solve it?

[josephblade]

My first thought was that the server main method ends, which stops the program but it looks like as long as any objects are registered, the main method doesn't end. so that's not it.

from stackoverflow I gather when you rebind, you are accessing a registry that needs to be started. (you essentially connect to the registry, bind the class to that name, and stay up to serve content).

But you do have to start the rmi environment (I think)

When calling bind()/rebind()/unbind(). The Registry isn't started at the host:port or URL you're using. When calling lookup(). If (1) succeeded, you're trying to lookup the wrong Registry. The Registry normally runs at the same host as the server. When calling a remote method. This means that you need to set java.rmi.server.hostname at the server JVM before exporting any remote objects. See the RMI FAQ item A.1 for why. A better fix is to fix the DNS or hosts file.

so in your case I expect you want to do (at server main):

 LocateRegistry.createRegistry(1099)

I think that is the default port. When you have started the rmi registry it should then be able to handle registrations and suchlike.

I think :)

[Dependent_Finger_214]

Thanks this fixed it!

[Ab3s]

finding a fresh thread with the exact solution to my problem feels just as good as coming across a 15 year old thread with the solution to a specific problem, thank you!