users@glassfish.java.net

RMI and garbage collection.

From: Russ Petruzzelli <Russ.Petruzzelli_at_Sun.COM>
Date: Tue, 20 May 2008 13:50:20 -0700

Regarding the server's jvm option: *|sun.rmi.dgc.server.gcInterval...

|*Currently the appserver sets this up to run a full GC every hour.

Documents state that RMI needs to force a GC to ensure remote objects
are unexported.

Why it is bad that the server doesn't know if a remote client has
dropped its reference to the server's exported remote objects?
(This is the stated reason for RMI forcing GCs.)

Is it that the remote jvm can't clean up its own objects in its JVM if
the server is still hanging on to it?
It seems the server, if left to its own devices, (ie no forced GCs) will
clean up whatever objects are unreferenceable in its own time, whether
RMI related or not.

Thanks,
Russ