RMI Server exits early when using SSL

Question

Hi,
Maybe someone else has encountered this one.
My RMI server works fine when I use standard sockets. I create an instance and bind it into the rmiregistry. It then waits indefinitely for connections.
When I use SSL, I can create the object instance. I can also bind it into the registry. However, it only waits a few seconds and then exits.
No exception or error is thrown (I have a catch Throwable block on my main method to be sure of this.)
As my code is adapted from the RMI SSL 'Hello World' examples found on this site) I decided to compile and run those examples. I get the same problem.
Any ideas?
This is the relevant part of my code:
public static void main(String[] args)
    HelloImpl obj = null;     
    try
        // use -clear option to get standard sockets
        if (args.length > 0 && args[0].equals("-clear"))
            obj = new HelloImpl();                   
        else // otherwise default to SSL sockets
            RMIClientSocketFactory csf = new RMISSLClientSocketFactory();
            RMIServerSocketFactory ssf = new RMISSLServerSocketFactory();
            obj = new HelloImpl(csf,ssf);               
        Naming.rebind("HelloServer", obj);
        System.out.println("HelloServer listening for requests\n";
    catch (RemoteException ex)
        ex.printStackTrace();
    catch (MalformedURLException ex)
        ex.printStackTrace();
    catch (Throwable ex)
        ex.printStackTrace();

Answer 1

Thanks for taking an interest.
I just use:
c:\j2sdk1.4.1_02\bin\rmiregistry
to start the registry.
I think the problem is with my SSL sockets. I'm guessing the reason a UnicastRemoteObject is normally kept alive (not garbage collected) in the registry is because it has a ServerSocket which is waiting for connections.
In this case, I don't think the SSLServerSocket is getting created and so my UnicastRemoteObject gets garbage collected.
However, I'm not sure why exactly.