Gerard BORREILL wrote: > Thank you very much for your answer, > > Maybe I will implement a distributed garbage collector. > > Who knows the exact consequences of having no distributed garbage > collector ? I think that it is exactly what you have experienced : memory leaks. Note that RMI/IIOP does not provide a garbage collector, which means that remote garbage collection must be implemented by the applications. > I would like to know if it implies that only the skeletons on the > server side are never collected, while the server is running. > I have a method in a Remote class that returns a Remote object. If a > client gets a remote reference on this object, and the client stops, > is my remote object never collected because it is related to its > skeleton ? I am afraid yes. The server is no more collectable as soon as it is exported (using the exportObject method, or a UnicastRemoteObject constructor). It becomes recollectable if it is unexported. Clients are not affected by this. Regards, Bruno PS : could you tell us what kind of project you're working on ?
begin:vcard n:Dumant;Bruno tel;cell:06 75 20 76 64 tel;fax:33 1 49 26 09 76 tel;work:33 1 42 44 40 74 x-mozilla-html:FALSE url:www.kelua.com org:Kelua SA adr:;;55 rue Sainte Anne;Paris;;75002;France version:2.1 email;internet:[EMAIL PROTECTED] x-mozilla-cpt:;1 fn:Bruno Dumant end:vcard
