RMI/IIOP explicity doesn't support distributed garbage collection (CORBA
doesn't provide support for it). See section 1.4.12 of the spec at
http://www.omg.org/cgi-bin/doc?formal/01-06-07.pdf
In practice, even if the EJB is passivated and reactived, the reference
to the remote object should still be valid unless the remote server has,
in the meantime, decided to destory it using
PortableRemoteObject.unexportObject(object)...
j.
Kenji Konaka wrote:
>hi!
>
>(I'm actually doing the similar thing, but..)
>
>what happens if that EJB (session) bean holding the Remote
>Object's rmi stub have got passivated and still if that rmi
>stub was the only dgc reference back to the Remote Object in
>the client JVM's Remote Object? -- I think the rmi stub
>stops updating the RMI dgc lease, and then eventually the
>Remote Object looses all the (dgc) reference and then get
>garbage collected; which then causes 'no object found' or
>'connection refused' exception next time the EJB side rmi
>stub have woken up and tried to some rmi method invocation
>back to the now deceased server object.
>
>(question here: on the client side JVM, if I've held some
>normal local object (hard) reference to the Remote Object, I
>think the Remote Object may still get rmi-``unreferenced'',
>but will it still be garbage collected then? if not so, 'rmi
>object not found' exception will happen next time the rmi
>stub did the method invocation?? --I think I may have to do
>some experiment myself on this...)
>
>for now, the way I think about this is that, if there was
>any other appropriate place to ``bind'' this Remote Object
>(like some rmiregistry within/or outside the EJB container),
>this might be better than to simply keep the rmi stub _only_
>in session beans...
>
>but I think there should be a much, much better way than this,
>I guess (some are already mentioned of course)...
>
>regards,
>kenji
>
> > From: "Peter J. Braswell" <[EMAIL PROTECTED]>
> > Date: Wed, 22 Aug 2001 06:13:34 -0400
> >
> > Ashish,
> > This could be accomplished if your client was a remote RMI object and
> > you passed a reference to your EJB during its invocation.
> >
> > cheers,
> > peter
>
>===========================================================================
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff EJB-INTEREST". For general help, send email to
>[EMAIL PROTECTED] and include in the body of the message "help".
>
>
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
