Help! Closing RMI Registry!

I'm using RMI and binding the registry to a port. However, if I close down the RMI application and re-start it, the registry is still bound to the port and causes errors. Is there any way I can shut-down the registry without having to kill it off manually?
Thanks.

Well, no, it isn't. If you start it from, say, a DOS prompt, then you have to kill the window by clicking on it and hitting CTRL-C.
Why not look up rmi.registry in the API guide and figure out how to start rmiregistry programmatically? I think the method is create() or createRegistry(). Sorry, too lazy to look it up myself.

Similar Messages

Can anybody help me to understand this RMI registry service code?

RMI is so difficult to me. please let me know following code what it means.
If this class is instantiated with 50000 port number,
Does RMI Registry Service get started with 50000 port number in place of rmiregistry commands?
And I don't have to execute rmiregistry command?
thanks in advance.
import java.rmi.AccessException;
import java.rmi.AlreadyBoundException;
import java.rmi.NotBoundException;
import java.rmi.Remote;
import java.rmi.RemoteException;
import java.rmi.registry.Registry;
import java.rmi.server.ObjID;
import java.rmi.server.RemoteServer;
import java.util.Enumeration;
import java.util.Hashtable;
import sun.rmi.server.UnicastServerRef;
import sun.rmi.transport.LiveRef;
* Registry implementation.
* @version 1.0
public class RegistryImpl extends RemoteServer implements Registry {
     private static final long serialVersionUID = -7162736590129110751;
     private Hashtable bindings;
    private static ObjID id = new ObjID(0);
     * @param i port number
     * @throws RemoteException
    public RegistryImpl(int i) throws RemoteException {
        bindings = new Hashtable(101);
        LiveRef liveref = new LiveRef(id, i);
        setup(new UnicastServerRef(liveref));
    private void setup(UnicastServerRef unicastserverref) throws RemoteException {
        super.ref = unicastserverref;
        unicastserverref.exportObject(this, null, true);
     * Lookup a remote object.
     * @param name Name of the remote object.
     * @return Remote object of the specified name.
    public Remote lookup(String name) throws RemoteException, NotBoundException {
//        Logger.debug("NamingService", "lookup: " + name);
        Remote obj;
        synchronized(bindings) {
            obj = (Remote)bindings.get(name);
            if(obj == null)
                throw new NotBoundException(name);
        return obj;
     * Binds the specified name to a remote object.
     * @param name A URL-formatted name for the remote object.
     * @param obj A reference for the remote object (usually a stub).
    public void bind(String name, Remote obj) throws RemoteException, AlreadyBoundException, AccessException {
//        Logger.debug("NamingService", "bind: " + name);
        checkAccess("Registry.bind");
        synchronized(bindings) {
            if(bindings.containsKey(name))
                throw new AlreadyBoundException(name);
            bindings.put(name, obj);
     * Destroys the binding for the specified name that is associated with a remote object.
     * @param name A URL-formatted name for the remote object.
    public void unbind(String name) throws RemoteException, NotBoundException, AccessException {
//        Logger.debug("NamingService", "unbind: " + name);
        checkAccess("Registry.unbind");
        synchronized(bindings) {
            if(!bindings.containsKey(name))
                throw new NotBoundException(name);
            bindings.remove(name);
     * Rebinds the specified name to a new remote object. Any existing binding
     * for the name is replaced.
     * @param name A URL-formatted name for the remote object.
     * @param obj A reference for the remote object (usually a stub).
    public void rebind(String name, Remote obj) throws RemoteException, AccessException {
//        Logger.debug("NamingService", "rebind: " + name);
        checkAccess("Registry.rebind");
        bindings.put(name, obj);
     * Returns an array of the names bound in the registry.
     * @return An array of the names bound in the registry.
    public String[] list() throws RemoteException {
        String[] names;
        synchronized(bindings) {
            int i = bindings.size();
            names = new String;
Enumeration e = bindings.keys();
while(--i >= 0)
names[i] = (String)e.nextElement();
return names;
* TO-DO
public static void checkAccess(String s) throws AccessException {
// check if s is in the list of agents.
if(true)
else
throw new AccessException("");
public static ObjID getID() {
return id;

You don't have any need to understand this code. The complication is due to the registry needing a fixed objectID.
You just need to know the methods of java.rmi.registry.LocateRegistry class. This allows you to start an RMI Registry inside your JVM and give it any TCP port number you like.

Bind to RMI registry on remote host

Is it possible to bing to a RMI registry on remote host. I get a Access exception when I try it. Is there is any work around for this?
Any help will be greatly appreciated.
Thanks
R

:Like I say, JINI uses a different model to RMI, and you can probably have a look at the forum for that here.
but a way around it is to create a server which listens for requests, accepts a remote object and a remote object name, and binds those into the registry on which its running - remember that the restriction only applies to registering objects, not to looking them up, so, once the object is registered on the remote host, it can be retrieved quite easily.
This of course leaves the problem of exception ahandling aside, but I trust the problems there are obvious

Port 1099 being used by other processes ,need an alt port for RMI-Registry

I am using port 1099 for RMI and the o/s is windows 2003.
We want that the RMI registry shud automatically be started with the windows startup processes.But we found that some other processes are usoing the same port.
Is there any other port which can be used for the same?
or any method to make other processes release the port forcefully.

If you read the documentation or do a quick google search, you will discover the rmiregistry program can be assigned any port you wish. Simply invoke via:
rmiregistry -h from windows or "man rmiregistry" from mac or unix and you will be greeted with:
Usage: rmiregistry <options> <port>
In a nut shell just specify the port:
i.e.
rmiregistry 5000
etc...
Hope this helps.
-Lemont

Error in re-creating RMI registry when reloading Tomcat server.

Hi,
I use LocateRegistry.createRegistry() in a servlet which is load-on-startup. I've unexport the registered remote object in the HttpServlet.destroy().
But when I reload the tomcat server, such an exception ocurrs:
java.rmi.server.ExportException: internal error: ObjID already in use
        at sun.rmi.transport.ObjectTable.putTarget(ObjectTable.java:168)
        at sun.rmi.transport.Transport.exportObject(Transport.java:69)
        at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:190)
        at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
        at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
        at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:145)
        at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92)
        at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:78)
        at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:164)
        at RmiUtils.rebindLocal(RmiUtils.java:86)Here is the binding code in RmiUtils.rebindLocal:
        try {
            Naming.rebind(url, rmiImpl);
        } catch (RemoteException ce) {
            if (!ru.isLocalhost()) {
                ce.printStackTrace();
                // cannot cache
                return;
            } else {
                // try to create the registry in local machine if not created
                try {
                    LocateRegistry.createRegistry(ru.getPort());
                    Naming.rebind(url, rmiImpl);
                } catch (RemoteException e) {
                    System.err.println("Failure in create Registry on port "
                            + ru.getPort() + ", maybe it's been created already!");
                    e.printStackTrace();// handle exception
        }Can anybody help?
Thanks.

Hi
I havent code for quite a while.
I would think that this wont work.
The registry is created on startup (possibly init method in ur servlet) but it is never destroyed.
You are better off starting the registry externally to ur servlet engine, and then use do a bind/rebind on startup, unbind on destroy.
Hope this helps.

Binding to RMI registry on remote host

Is it possible to bing to a RMI registry on remote host. I get a Access exception when I try it. Is there is any work around for this?
Any help will be greatly appreciated.
Thanks
R

This is the same problem I ran into. Unfortunately there is no way around this. I had to abondon using RMI registry and instead I changed my program to use the tnameserv/orbd stand-alone naming services in a typical JNDI fashion. This tutorial has some examples, good luck:
http://java.sun.com/j2se/1.4.1/docs/guide/rmi-iiop/tutorial.html

RMI Registry leaves thread running

I've searched the postings about this topic and none of them have been helpful. I create an RMI registry at port 1099 in my app, use it, and then try to shut it down, but it leaves a thread running.
The following sample code shows what my code does (in a condensed form):
Registry registry = LocateRegistry.createRegistry(1099);
Communicator c = new CommunicatorImpl();
registry.rebind("//localhost/remoteserver", c );
Naming.rebind("rmi://localhost:1099/TriggerService", c);
registry.unbind("//localhost/remoteserver");
Naming.unbind("rmi://localhost:1099/TriggerService");
boolean b = UnicastRemoteObject.unexportObject(registry, true);
System.err.println( "unexported: "+b );When I run this code in Eclipse and the code exits, I still have a process running that was spawned by "LocateRegistry.createRegistry(1099)", but I can't figure out how to get a handle for it within my program, so that I can kill it. I've read that it will end when the JVM ends, but the RMI portion of my app is only a small part and I need the rest of it to keep running. Is there a way to stop this thread?
Thanks,
Tony

Well I only see 'createRegistry' and 'getRegistry' I don't see any 'destroyRegistry' methods. So I don't know.
What I used to do back in the day was to use Runtime to start an external process for processes that I needed to kill later on. So perhaps you can use the runtime to start the registry from the command line so to speak. Then hold a reference to the returned process. Then you can kill that process when you want the registry to die. In this case you will for sure be creating a new 'jvm' for the registry to run within. (if the registry is a java program)
Otherwise I have no idea why you would be seeing an extra java process. If you run the eclipse debugger, the debugger should not exit until the whole process is done. Even when the program is done, the debugger will still be 'live' and you can push the stop button to stop the whole launched process.

RMI Registry

Hi!
Is it possible to install more then one RMI Registry service
in the same machine? If so, how can the clients make the
distinction between objects ?
Thanks!

Yes, just bind each "registry" to a different port. The default port is 1099. So, for example, you can bind a "registry" to port 1098 with the following command:
rmiregistry 1098Of-course, if port 1098 is already being used, the above command will fail -- and you will get an error message.
Hope this helps.
Good Luck,
Avi.

RMI Registry Workaround

Hi,
I don't want to start RMI registry for my server in different window. How can i bind my remote object without starting RMI Registry externally. I think it can be done , but how i don't know.
Please help
Ritesh Alagh

Read the APIs...
http://java.sun.com/j2se/1.4.2/docs/api/java/rmi/registry/LocateRegistry.html

Run rmi registry in executable

Hi all,
I've created a jar executable for an application I wrote. I have two questions if anyone can help me out with either.
1. Is there anyway to have it run my rmi registry along with the jar executable so I don't have to run it seperate?
2. Is there anyway that I can make a .exe executable for a user that doesn't have jre for free? I've found some programs that will do it for me, but I have to purchase them. I'd also like to avoid converting all my code into another language first.
Any help would be appreciated. Thanks
Leon

1. java.rmi.registry.LocateRegistry.createRegistry().
2. There is GCJ, but I don't recommend it.

Help! RMI throws NoSuchMethodError

Everything goes fine. The rmiregistry starts, server code starts. The binding takes place properly but when u do
Test test = (Test)Naming.lookup( "rmi://localhost/test")
it gives this :
Exception in thread "main" java.lang.NoSuchMethodError: stub class initialization failed at TestImpl_Stub.<clinit>(Unknown Source)
at java.lang.reflect.Field.getLong(Native Method)
at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:415)
at java.security.AccessController.doPrivileged(Native Method)
at java.io.ObjectStreamClass.init(ObjectStreamClass.java:401)
at java.io.ObjectStreamClass.lookupInternal(ObjectStreamClass.jav
at java.io.ObjectStreamClass.setClass(ObjectStreamClass.java:566)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:366)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1186)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
at java.rmi.Naming.lookup(Naming.java:84)
at TestClient.getHost(TestClient.java:68)
at TestClient.initialise(TestClient.java:102)
at TestClient.<init>(TestClient.java:17)
at TestClient.main(TestClient.java:132)
Any clues???

Well, I'm sure this isn't it, but I've never seen "rmi://.....". I always just use "//...". Anyways, you could try something like:
Regisry r = LocateRegistry.getRegistry("127.0.0.1", 1099);
RMIInterface t = (RMIInterface) r.lookup("//127.0.0.1/test");This probably won't change things, but you never know. Now, it seems like your maybe missing something on the server side. When you start your rmi server, maybe try specifying the codebase and server name:
java -cp . -Djava.rmi.server.hostname=127.0.0.1 -Djava.rmi.server.codebase=. -Djava.security.policy=./java.policy RMIServerAlso, how do you start rmiregistry? From the command line or in your source? You can create the registry from the main method of your RMIServer class:
public class RMIServer extends UnicastRemoteObject implements RMIInterface {
public static void main(String[] args) {
Registry r = LocateRegistry.createRegistry(1099);
RMIServer theServer = new RMIServer(31415);
r.rebind("//127.0.0.1/someService", theServer);
public RMIServer(int port) throws RemoteException {
super(port);
}This creates an rmi registry at port 1099, and creates your service at port 31415 with the name "someService" on a server called "127.0.0.1". If you combine all of these, I think it should work. I am of course assuming that the stubs and skeletons are being generated, and then deployed with the client app appropriately. Hope this helps.
m

Unable to contact the RMI registry

Can anyone please help with this error?
exception: flex.messaging.MessageException: Unable to contact
the RMI registry on 'localhost' to look for the oldFusion Data
Management Service: java.rmi.onnectionIOException: error during
JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read time out.
This is a previously working flex app, but a fresh install of
ColdFusion 7 and I've enabled FDS in CF Admin.

Can anyone please help with this error?
exception: flex.messaging.MessageException: Unable to contact
the RMI registry on 'localhost' to look for the oldFusion Data
Management Service: java.rmi.onnectionIOException: error during
JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read time out.
This is a previously working flex app, but a fresh install of
ColdFusion 7 and I've enabled FDS in CF Admin.

RMI registry weirdness, API versioning, and more

Hi folks,
     I have some RMI questions. I'd like to start by giving background on the software and our intentions with RMI.
     Our software is a molecular biology analysis and simulation tool. Since the technology is very proprietary, we've used RMI to split the Java software into a front-end GUI client that that's distributed to users and a back-end server that makes use of our in-house C++ tools.
     At the moment our user base is small, mostly a handful of academic researchers, but even with these few releases are getting difficult to manage. The problem, of course, is that when the server back-end is upgraded, if any serializable or remotable APIs are changed, the user must also upgrade their client. Our users have made it clear that this is an unacceptable inconvenience, and since we frequently push new feature-filled releases, its difficult to keep the APIs stable. Additionally, 40% of the original code base is absolute tripe, the inflexible, ill-thought, and monolithic work of a contractor who was at at deadline and had to 'just get the job done'. With only two developers (one of them part-time), we are forced to rewrite portions of this old code in small spurts as most of our time is taken up either adding features or working on the C++ tools. In short, there's simply no way we can stabilize our APIs at this time.
     My first (perhaps naive) solution was simple: the client/server pair are built with a common API version number that is incremented each time the API of a serializable or remotable API must be changed for a new release. This version number is appended to the RMI URI for the server. For example, when using API version 13, if the back-end service is told to listen on the following URI:
     //remote.mycompany.com/myobject
...the back-end would implicitly bind to...
     //remote.mycompany.com/myobject-13
     Since the client and server are built with the same API version, the client knows to append -13 to whatever URI the user specifies to connect to a back-end with a compatible API. This lets the user think they're connecting to the 'usual' URI, but allows us to run servers with varying APIs concurrently on the same physical machine, thus our users can upgrade at their leisure and we can push new releases whenever we please.
     I prefer this solution because its very non-intrusive code-wise and allows us developers complete freedom, but it seems prone to subtle problems. We have three releases (hence three servers) and clients are able to function initially, but eventually they start reporting not-bound and class UID/checksum errors - exactly what this system is supposed to prevent. The three services appear to work when started initially but fail sporadically after some period of time. It seems to me that the RMI registry is getting confused when deciding which classes from which service should be sent to which client.
     I should note that rmiregistry requires us to pass in the path to our classes to its JVM (with -J) or it throws NoClassDefFoundError errors when a client connects to the back-end service (if memory serves, our logger is the offending class, so perhaps the registry is executing a static initializer that prints log messages or something). We only pass in the path to one set of classes right now (the oldest of our API revisions). I'm not sure if passing all three would help, but I don't see how it would, and I really don't have the time to experiment. Interestingly, this class path requirement only started happening a few weeks ago - previously rmiregistry didn't seem to care where our logging classes were. I'm not sure if this is contributing to the concurrency problem stated above, but if there's reasonable suspicion I'm more than happy to figure out why this is happening. Also, I remember reading on some web site that setting the rmiregistry class path with -J could cause other strange problems relating to RMI stubs, so could this be a likely suspect? I wish I was more familiar with the guts of RMI as to know what's going on in the registry. Should I be seeing such problems when binding multiple versions of the same class instance?
     I suppose I'd really like, aside from the informed opinions and suggestions of experienced Java programmers, is an architectural overview of the RMI implementation so I can answer these questions myself, but I haven't found anything in that vein. Ideally I'd like to look at the code for the RMI implementation. Is this possible? I'm not 'hip' to Sun's code sharing policies, what portions of their code base they open up if any. Can anyone offer any hints?
     We did come up with some other possible solutions for the API versioning problem. Dynamic class loading via HTTP in particular is my next best hope. Tentatively speaking, it seems that this would help minimize API breakage so long as modifications are limited to adding elements to the API and not removing them. It seems to me that allowing users to download classes at runtime would allow us developers more flexibility, even though users would be forced to upgrade every once in a while, albeit less frequently than they otherwise would.
     Also considered was a separate tool for automated management of the client software, i.e., an auto-update utility. I'd rather not go down this path; I think it would annoy our users, and our two-man development team is busy enough without worrying about more cruft.
     Any additional suggestions are welcome, as is any insight into the Sun's RMI implementation. Advice, links to documentation, "hey stupid, google for <somthing obvious>" would be appreciated.
Cheers :-)
-Nick

or you could buy mine (http://www.rmiproxy.com/javarmi), but I'll give you three tips:
(1) If possible don't change existing interfaces, just extend them, i.e. version them by extending them:
public interface MyRemoteVersion1 extends Remote {}
public inteface MyRemoteVersion2 extends MyRemoteVersion1 {}This way old clients can still use the old services even if they receive a newer stub.
(2) Do the same with the implementations, and load & register both, with different names as ou are doing. Don't use the same class name for a new version otherwise you will confuse the class loader. Altneratively you could use different class loaders for teh different versions to keep them separate, but that's a large can of worms.
(3) Ignore your feelings about the code base. It's installed out there and it's a product now, you just have to live with it unless you can instaneously upgrade all your clients, which you can't. You will probably always have a client running the original version for reasons entirely beyond your control.
(4) Do use the codebase feature if you possibly can. Don't install anything at a client that it could get via a codebase, e.g. stubs. The only thing that clients should need is the remote interfaces and the the true client code.
(5) Make sure every version of every marshalled class has the same setversionuid and make sure that this is there from the beginning. Make sure you only evolve these classes in ways which will be compatible under serialization - see the spec.
Good luck
EJP

Simple question about java.rmi.registry.Registry

Hi,
where the object java.rmi.registry.Registry takes a URL to rmiregistry when perform bind method.
thanks.

Ok, will try to explain.
I have a server that I register in the RMI registry. Client from a remote machine get the server (as a remote object) and calls his method for the generation of another object on the parameters passed. The server creates this object and tries to register it in the RMI registry, and this raises an exception Registry.Registry.rebind disallowed; origin /11.0.10.31 is non-local host.
11.0.10.31 is a IP - address of the client

Is the RMI registry "process-atomic"?

Hi,
Sorry if this is a really stupid question, and I have really tried to find this out on my own.
When I say "process" I mean Process, as opposed to Thread.
What I mean is, if one Process calls Registry.bind( String, Remote ), can we be sure that another Process which does the same thing one nanosecond later will get an AlreadyBoundException if it calls with the same String?
The context is that up to now I have been starting the RMI Server (only for logging at the mo, these are my first steps) explicitly in a Process. But now I want to move to "lazy" startup of the RMI registry and of the Server... so I would go LoggerInterface.log( bindingName, message ), and if the name "bindingName" is not presently in the registry it will create a new Server, and log the message using it.
More specifically, this is about me trying to automate OpenOffice apps using Java... and it occurs to me that 2 events could indeed happen almost simultaneously, so in fact even explicitly starting up the Server in each handler module might encounter "Process concurrency" problems ... so I need to have an answer to this.
I hope the answer is yes... otherwise I'm going to be a bit flummoxed about how to ensure one doesn't start up one Server Process from one calling Process, and another Server Process from another calling Process.
Thanks

I mean to use rebind() instead of the lookup()/bind() pair. It is atomic.... I understand it is atomic, but my point is that between checking whether you need to rebind (because the bound stub is invalid) and actually doing the rebind there will be an interval. If you systematically use rebind, without a prior check to make sure your Remote is actually attached to an existing Process, every call will cause a new Server Process to be created and then rebound, one after another. Which would be a mess.
I'm going to spend a bit of time looking at your two references... thanks for them.
I have thought of a possible solution involving a sort of lock, but I'm not sure if it works.
1. create a "DummyInterface" extending Remote:
public interface DummyInterface extends Remote {
}2. in the Process + Thread which actually sets up the Registry, bind a DummyInterface
Registry reg = null;
try {
reg = LocateRegistry.createRegistry( 1099 );
} catch (RemoteException e) {
return; // is this right? see below...
DummyInterface dummyStub = new DummyInterface(){};
try {
dummyStub = (DummyInterface) UnicastRemoteObject.exportObject( dummyStub, 0);
} catch (RemoteException e) {
// TODO sthg
e.printStackTrace();
try {
reg.bind( "DummyLockForLoggerServer", dummyStub );
} catch (AlreadyBoundException e) {
// every Thread in every Process (except the first such) to call "bind" will get here
return;
} catch (Exception e) {
// TODO sthg
e.printStackTrace();
}3.     the first Process + Thread which wants to set up the LoggerServer will have first to unbind the DummyLock.
try {
   reg.unbind( "DummyLockForLoggerServer" );
} catch (AccessException e) {
   // TODO sthg
   e.printStackTrace();
} catch (RemoteException e) {
   // TODO sthg
   e.printStackTrace();
} catch (NotBoundException e) {
// every Thread in every Process (except the first such) to call "unbind" will get here
return;
// only one Thread in one Process will ever succeed in getting here
// start the LoggerServer
String qualifiedClassName = ".... rmi.LoggerServer";
String[] a_commandArgs = { "java", qualifiedClassName, "logName" };
Process process = null;
try {
process = Utils.runSubprocess(a_commandArgs, null, ProcessSettings.getJavaRootDir());
} catch (IOException e) {
   // TODO sthg
   e.printStackTrace();
}... however there seem to be one or two questions about this:
- does reg = LocateRegistry.createRegistry( 1099 ); throw a RemoteException if the Registry is already bound? I don't know and intend to do a few experiments to find this out for myself. But in any event only one Process+Thread can ever bind the dummy lock
- there might be a race condition nonetheless to do with the interval between creating the Registry and binding the dummy lock... during this interval the Registry is established, and the dummylock is not yet set up... but I think this does no harm, as a Process trying to start the LoggerServer during this time will get the "NotBoundException" and simply return (and the calling thread will then sleep for a bit before trying again).

Help! Closing RMI Registry!

Similar Messages

Maybe you are looking for