Naming.lookup() strange behavior

[Richard Everhart]

Okay, this is strange to me but perhaps not to you.

I've started the RMI registry on my computer doing the following:

RMIService service = new RMIServiceImpl(dbFileName);
Registry registry = LocateRegistry.createRegistry(Registry.REGISTRY_PORT);
registry.rebind("Service", service);            

I then try to start the client by doing this:

  
RMIService service = (RMIService)Naming.lookup("//remoteHost/Service");

The client connects with the registry fine when I enter 127.0.0.1, and the name of the machine itself. It also reacts appropriately when the user has entered an incorrect host name or IP address. However, if remoteHost is the string 'qwerty127.0.0.1' or '127.0.0.1qwerty' or '127.a.0.0.1' or even empty string it works. It doesn't work, though, when I enter some junk string like just 'qwerty' or if remoteHost is some variation of the loopback IP like 127.1.0.1.

It seems that somehow by default, when the remote host is specified a certain way, the localhost is contacted to obtain the remote object. I still have not tried out my code anywhere else except my computer so I'm not sure if I'll have different behavior doing this or not.

Thanks!

Rich

[Andrew Monkhouse]

Hi Rich,

I don't think that you need to worry about for your assignment. This sounds like a JVM / RMI implementation issue, and it is really out of your hands.

Regards, Andrew