Security & Policy file

[Michael Nadel]

When I run my client on one machine, and the server on another, I get the following on the client error every time I try communicating with the server via RMI:
java.rmi.ConnectException: Connection refused to host: 127.0.0.1
This looks like a different error than the usual message received when the policy file is set up incorrectly.
Any ideas?
TIA,
michael
My policy file is:
grant {
permission java.security.AllPermission;
permission java.net.SocketPermission "*:1024-65535", "connect,accept,resolve";
permission java.net.SocketPermission "*:1-1023", "connect,resolve";
}

[Trevor Dunn]

Hi,
I just struggled with a ConnectException. In research I found that there is a common bug in RMI that has something to do with not being able to resolve the host name. One of the solutions was to provide the command line argument
-Djava.rmi.hostname=hostname
I am not sure if this is your problem. As it turned out it was not my problem. The one I had was that I was calling LocateRegistry.getRegistry(name, port) to see if an instance of the registry was already running. As it turns out, even if there is not a registry running this call returns a Registry object anyway that does not work.
I hope this helps
Trevor