Question

To make a long story short, I’m having trouble getting a couple of Java RMI’s non-daemon threads to close out after my application no longer needs RMI. This prevents the JVM from exiting when main() completes.

I understand that exporting UnicastRemoteObjects will cause RMI to leave threads open until you successfully call UnicastRemoteObject.unexportObject(Object o,boolean force). Here’s an example (run without modification and the JVM will exit normally – remove the call to unexportObject and the JVM will never exit):

import java.rmi.registry.LocateRegistry;
import java.rmi.registry.Registry;
import java.rmi.server.UnicastRemoteObject;

public class TestUnicastRemoteObject{
private static UnicastRemoteObject obj;
private static Registry registry;

public static void main(String[] args) throws Exception{
    obj = new UnicastRemoteObject(){
        private static final long serialVersionUID = 1L;
    };
    System.err.println("created UnicastRemoteObject");
    System.err.println("creating registry ...");
    registry = LocateRegistry.createRegistry(9999);
    System.err.println("registry created.");
    System.err.println("binding obj to registry ...");
    registry.bind("Test", obj);
    System.err.println("bound");
    UnicastRemoteObject.unexportObject(obj, true);
    System.err.println("unexported obj");
}
}

Also, it doesn’t seem to matter whether you create the registry and/or bind the remote object to it – the only thing that seems to matter in this example is that any time you create a UnicastRemoteObject, you need to call unexportObject in order to prevent any threads from remaining after you’re done.

In my application, I’ve made sure that I’ve called unexportObject on every UnicastRemoteObject I create, and yet RMI’s “reaper” thread and “connection accept” thread still persist, preventing my JVM from exiting when my application is finished using RMI resources.

Is there something else that could cause RMI to leave threads behind, aside from forgetting to unexport UnicastRemoteObjects?

Answer 1

Sure enough, I had a bug in the code that caused one of my (many) UnicastRemoteObjects to not unexport itself when the calling application was done utilizing it. So the answer is:

Unexporting all UnicastRemoteObjects within a running JVM is sufficient to close all RMI non-daemon threads.