rmiregistry: The Java RMI Object Registry

rmiregistry: The Java RMI Object Registry

JDK 1.1 and later

---

Synopsis

     rmiregistry [ port ]

Description

The rmiregistry command starts a remote object naming registry on the current host. The RMI registry binds remote objects to names, so that remote clients can request object references by name. It uses the object references to invoke methods.

Internally, the rmiregistry command uses the java.rmi.registry.LocateRegistry class to instantiate a registry object. If no port is provided, the default port for the registry is 1099. Typically, the registry is run in the background on a server and remains running for the lifetime of the objects it contains. If the registry crashes and the registry is running in a separate Java VM from the actual remote objects, the remote objects are still available over RMI, and any remote references to these objects that existed before the crash are still valid. However, all the name bindings the objects had in the registry are lost and need to be re-created after a new registry is started.

Options

-J[javaoption]

Anything immediately following the -J is passed as an option to the underlying Java interpreter. There should be no spaces between the -J and the option to be passed to the interpreter.

Environment

CLASSPATH

An ordered list of directories, zip files, and/or jar files the rmiregistry command uses to look for classes. This list is separated by colons in Unix environments and semicolons in Windows environments. It is searched, in order, for a given class when it is encountered during execution. The registry automatically appends the system CLASSPATH to the classpath, if it is specified. If the CLASSPATH isn't set in the environment, the daemon uses the current directory and the system CLASSPATH as its classpath.