Unicast Remote Object Interface


Unicast Remote Object

The UnicastRemoteObject class defines a non-replicated remote object whose references are valid only while the server process is alive. TheUnicastRemoteObject class provides support for point-to-point active objectreferences (invocations, parameters, and results) using TCP streams.

The class java.rmi.server.UnicastRemoteObject provides support for creating and exporting remote objects. The class implements a remote server object with the following characteristics:

  • References to such objects are valid only for, at most, the life of the
  • process that creates the remote object.
  • Communication with the remote object
  • It uses a TCP transport.
  • Invocations, parameters, and results use a stream protocol for communicating between client and server.


package java.rmi.server;
public class UnicastRemoteObject extends RemoteServer {
protected UnicastRemoteObject()
throws java.rmi.RemoteException;
protected UnicastRemoteObject(int port)
throws java.rmi.RemoteException;
protected UnicastRemoteObject(int port,
RMIClientSocketFactory csf,
RMIServerSocketFactory ssf)
throws java.rmi.RemoteException;
public Object clone()
throws java.lang.CloneNotSupportedException;
public static RemoteStub exportObject(java.rmi.Remote obj)
throws java.rmi.RemoteException;
public static Remote exportObject(java.rmi.Remote obj, int port)
throws java.rmi.RemoteException;
public static Remote exportObject(Remote obj, int port,
RMIClientSocketFactory csf,
RMIServerSocketFactory ssf)
throws java.rmi.RemoteException;
public static boolean unexportObject(java.rmi.Remote obj,                                                     boolean force)
throws java.rmi.NoSuchObjectException;

Constructing a New Remote Object

  • A remote object implementation (one that implements one or more remote interfaces) must be created and exported.
  • Exporting a remote object makes that object available to accept incoming calls from clients.
  • For a remote object implementation that is exported as a UnicastRemoteObject, the exporting involves listening on a TCP port (note that more than one remote object can accept incoming calls on the same port, so listening on a new port is not always necessary).
  • A remote object implemention can extend the class UnicastRemoteObjectto make use of its constructors that export the object, or it can extend some other class (or none at all) and export the object via UnicastRemoteObject’s exportObject
  • The no argument constructor creates and exports a remote object on an anonymous (or arbitrary) port, chosen at runtime.
  • The second form of the constructor takes a single argument, port, that specifies the port number on which the remote object accepts incoming calls.
  • The third constructor creates and exports a remote object that accepts incoming calls on the specified portvia a ServerSocket created from the RMIServerSocketFactory; clients will make connections to the remote object via Sockets supplied from the RMIClientSocketFactory.

 Exporting an Implementation Not Extended From RemoteObject

  • An exportObjectmethod (any of the forms) is used to export a simple peer-to-peer remote object that is not implemented by extending the UnicastRemoteObject
  • The first form of the exportObjectmethod takes a single parameter, obj, which is the remote object that will accept incoming RMI calls; this exportObject method exports the object on an anonymous (or arbitrary) port, chosen at runtime.
  • The second exportObjectmethod takes two parameters, both the remote object, obj, and port, the port number on which the remote object accepts incoming calls.
  • The third exportObjectmethod exports the object, obj, with the specified RMIClientSocketFactory, csf, and RMIServerSocketFactoryssf, on the specified port.
  • The object mustbe exported prior to the first time it is passed in an RMI call as either a parameter or return value, otherwise, a rmi.server.StubNotFoundException is thrown when a remote call is attempted in which an “unexported” remote object is passed as an argument or return value.
  • Once exported, the object can be passed as an argument in an RMI call or returned as the result of an RMI call.
  • The exportObjectmethod returns a Remote stub which is the stub object for the remote object, obj, that is passed in place of the remote object in an RMI call.

Passing a UnicastRemoteObject in an RMI Call

  • As stated above, when an object of type UnicastRemoteObjectis passed as a parameter or return value in an RMI call, the object is replaced by the remote object’s stub.
  • A remote object implementation remains in the virtual machine in which it was created and does not move (even by value) from that virtual machine.
  • In other words, a remote object is passed by reference in an RMI call; remote object implementations cannot be passed by value.

Serializing a UnicastRemoteObject

  • Information contained in UnicastRemoteObjectis transient and is not saved if an object of that type is written to a user-defined ObjectOutputStream (for example, if the object is written to a file using serialization).
  • An object that is an instance of a user-defined subclass of UnicastRemoteObject, however, may have non-transient data that can be saved when the object is serialized.
  • When a UnicastRemoteObjectis read from an ObjectInputStream, it is automatically exported to the RMI runtime so that it may receive RMI calls. If exporting the object fails for some reason, deserializing the object will terminate with an exception.


Unexporting a UnicastRemoteObject

  • The unexportObjectmethod makes the remote object, obj, unavailable for incoming calls.
  • If the force parameter is true, the object is forcibly unexported even if there are pending calls to the remote object or the remote object still has calls in progress.
  • If the force parameter is false, the object is only unexported if there are no pending or in-progress calls to the object.
  • If the object is successfully unexported, the RMI runtime removes the object from its internal tables.
  • Unexporting the object in this forcible manner may leave clients holding stale remote references to the remote object.
  • This method throws java.rmi.NoSuchObjectException if the object was not previously exported to the RMI runtime.

The clone method

  • Objects are only clonable using the Java language’s default mechanism if they support the lang.Cloneableinterface.
  • The class rmi.server.UnicastRemoteObjectdoes not implement this interface, but does implement the clone method so that if subclasses need to implement Cloneable, the remote object will be capable of being cloned properly.
  • The clonemethod can be used by a subclass to create a cloned remote object with initially the same contents.