Problem with binding...

[Sean Keane]

Hi, I am new to RMI and just playing around with a toy example, but I am having problems! So wondering if anyone can steer me in the right direction?

I am following an example from the book Core Java, Vol. 2: Advanced Features 8th Edition (page 849) http://www.amazon.com/Core-Java-Vol-Advanced-Features/dp/0132354799/ref=sr_1_1?ie=UTF8&qid=1298533409&sr=8-1

The code is quite simple, I am just trying to start up the server, here's the code:

package core.java.book.chpt10.example;

import java.rmi.RemoteException;

import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;

public class WarehouseServer {
	
	public static void main(String[] args) throws RemoteException, NamingException {
		System.out.println("Constructing server implementation...");
		WarehouseImpl centralWarehouse = new WarehouseImpl();
		
		System.out.println("Binding server implementaiton to registry...");
		Context namingContext = new InitialContext();
		namingContext.bind("rmi:central_warehouse", centralWarehouse);
		
		System.out.println("Waiting for invocations from clients...");
	}
}

But when I try this, I get the error below. I have turned off Windows firewall. I understand when you don't specify a URL or port that the localhost will be used and port 1099 - I've checked that port 1099 is not in use, and my IP address is indeed 172.16.160.17 as per the error message. So I'm a bit unsure of how to resolve this issue. Any ideas?

Constructing server implementation...
Binding server implementaiton to registry...
Exception in thread "main" javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 172.16.160.17; nested exception is: 
	java.net.ConnectException: Connection refused: connect]
	at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:126)
	at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
	at javax.naming.InitialContext.bind(InitialContext.java:400)
	at core.java.book.chpt10.example.WarehouseServer.main(WarehouseServer.java:17)
Caused by: java.rmi.ConnectException: Connection refused to host: 172.16.160.17; nested exception is: 
	java.net.ConnectException: Connection refused: connect
	at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)
	at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
	at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
	at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322)
	at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
	at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:120)
	... 3 more
Caused by: java.net.ConnectException: Connection refused: connect
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
	at java.net.Socket.connect(Socket.java:529)
	at java.net.Socket.connect(Socket.java:478)
	at java.net.Socket.<init>(Socket.java:375)
	at java.net.Socket.<init>(Socket.java:189)
	at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
	at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
	at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
	... 8 more

[Edward Harned]

You need a security policy file such as:
grant {
permission java.security.AllPermission "", "";
};

You'll also need a classpath so the RMI Registry can find your generated stub.

[Sean Keane]

Thanks. I created a file called security.policy in the same folder as my .class file that contained:

grant {
permission java.security.AllPermission "", "";
};

I then ran the following command

java -cp .  -Djava.security.policy=security.policy WarehouseServer 

and got the exact same error, any suggestions?

[Edward Harned]

It still looks like a security problem.

The registry also needs a security policy file as well as a classpath. The registry is realty a Java application too.
-J-Djava.security.policy=
-J-Dclasspath=

These problems happen to everyone. Once you get everything set up, it will all work fine.