RMI registry is the binder for Java RMI. An instance of RMI registry must run on every server computer that hosts remote objects. It maintains table mapping textual, URL style names to refer remote objects hosted on that computer. Naming class provides methods for RMI registry :
rebind(String name, Remote object) bind(String name, Remote object) unbind(String name, Remote object)
The OSagent is a process that allows CORBA servers to register their objects and assists client applications in the location of objects. The OSagent is designed to be operated on more than one node.This is done to avoid a single point of failure. OSagent processes follow a set of rules to discover each other and cooperate in the location of registered objects.
The difference between unicast and multicast is that in unicast approach the sender sends the data stream to a single receiver at a time. Thus there is one to one communication.
In a multicast the sender and the interested receivers communicate. This is one to many communication. This communication can take place between data terminals spread across various LANs too.
The java.net.UnknownHostException method is used as remote calling and for callback routine fail. RMI uses default settings to resolve the server hostname like WINS names, DHCP names, etc. This happens due to which RMI client invokes the remote method using the reference that consists of unresolved server hostname and the client will produce UnknownHostException. RMI servers provide fully qualified hostname or IP address to resolve all RMI clients error reports. RMI provides an operation to remotely callback a program that serves RMI object and provide resolvable hostname to pass it to the RMI clients. UnkownHostException is thrown when an applet is failed to provide a useable server hostname. The property java.rmi.server.hostname can be set to get from the server the correct IP address or hostname.