From: ara.t.howard@...
Date: 2007-03-27T23:39:29+09:00
Subject: Re: drb recycled object problem

On Tue, 27 Mar 2007, Raj Sahae wrote:

> ara.t.howard@noaa.gov wrote:
>> yeah.  terrible idea.
>> 
>> you just need to keep a reference to it to prevent it from being gc'd.  can
>> you show use some code?
>> 
>> -a

> Snipping code would be tricky.  It's a fairly large program.  None of the 
> objects that are important are ever, EVER, not referenced somehow.

but the error is telling you that this is exactly what's happening?

> Everything is stored in arrays, and transferred around in arrays.  Objects
> on the server are moved from array to array by the client calling methods
> using DRb.  What kind of code would you want me to show you to prove this?

it's like this; there are two possibilities:

   1) you've found a bug in ruby and/or drb

   2) you are not actually keeping a reference on every object the client gets
   a remote reference on and some object(s) is being collected

given that drb is heavily used and mature it's probably wise to spend time
tracking down #2.  if you're going to look into #2 there is probably help on
this list.  basically you need to figure out which object is being lost and
track its lifecycle on the server.

regards.

-a
-- 
be kind whenever possible... it is always possible.
- the dalai lama