The lack of distributed garbage collection should not be the only source of the memory
leak. Make sure your EJB-container uses EJB pools rather than instantiating a
new server object for each 'create' or 'find' call on the home interface.
Peter
> Hello, A distributed garbage collector unexports remote objects that are no more
>used
> by any client within a timeout. Thus it allows the garbage collector to remove
> from memory these objects. So you have to call explicitely the unexportObject()
>method on the remote
> objects that are no more used by any remote client (here your session bean). Example:
> UnicastRemoteObject.unexportObject(myBean, true); Regards, G�rard Borreill,
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonathan".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
