You guessed correctly, but I realized that I'm using a class with static
initialization in two different VM's and my static initialization was
rebinding a new instance of the remote object when the class loader in the
second VM loaded the class.
Thanks for the help.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Rickard �berg
Sent: Thursday, October 26, 2000 11:09 AM
To: jBoss
Subject: Re: [jBoss-User] Problems with RMI
Hi!
Robert Taylor wrote:
> I have created and successfully deployed a TestBean.
> It uses an object which makes an RMI call to another object to do some
work.
> Sometimes the following stack trace is printed upon looking up the RMI
> object
> although no exception is thrown.
<snip>
> Subsequent calls to methods on the RMI object throw
> java.rmi.NoSuchObjectException
>
> It looks as though the object is becoming unbound from the naming service.
> That's guess.
Are you binding it into our JNDI tree? (I'm guessing yes)
Are you storing the reference to your remote object so that it is not
GC'ed? (I'm guessing no)
If both above guesses are right, then the fix is to hold on to your
remote object somehow. If you are creating it through an MBean, keeping
a reference to it in the MBean would be a good solution.
regards,
Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
