Mailing-List: contact river-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: river-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4B92027D.7030001@qcg.nl>
Date: Sat, 06 Mar 2010 08:21:33 +0100
From: QCG - Sim IJskes <sim@qcg.nl>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: river-dev@incubator.apache.org
Subject: Re: strange problem with DGC
References: <4B8F86B0.6080305@qcg.nl> <4B903484.40701@zeus.net.au>
 <4B9036BA.8010701@zeus.net.au> <4B903A8B.3010508@zeus.net.au>
 <4B90E229.6060604@qcg.nl> <4B919A93.3070201@zeus.net.au>
In-Reply-To: <4B919A93.3070201@zeus.net.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Peter Firmstone wrote:
>> The problem starts when you marshall it in 
>> BasicInvocationDispatcher.marshalReturn(), and the reply has enough 
>> latency to arive 'late' at the client side.
>>
>> In this window the service becomes 'weakly reachable' and if the GC 
>> kicks in before DgcServer.dirty the object gets finalized.
> 
> Keep a strong reference, to the service (not the proxy), long enough to 

Indeed, but my point is, that this is so counter-intuitive. It looks 
like this is completely overlooked by the design of jini. Why? I can't 
imagine. Everywhere where you have a service that has a factory method 
for a service, and you don't register the service or save the service 
reference, this will happen. It has never been documented.

It is because GC has become better? Shouldn't we include a fix in the 
BasicJeriExporter for this?

Gr. Sim