river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Firmstone <j...@zeus.net.au>
Subject Re: strange problem with DGC
Date Thu, 04 Mar 2010 22:30:28 GMT
Sim IJskes - QCG wrote:
> Hello,
> i've got a strange problem with DGC.
> In a service, we create a service, export it with DGC, keep no 
> reference  of the service or exported service on the service side, 
> return it immediately to the caller.
> The expected behaviour is that from the moment of export, we get a 
> certain period for the exported service to be deserialized at the 
> caller side, and do our first DgcServer.dirty call.
> It turns out, that ObjectTable$Target.collect is called before the 
> first dirty call is done.
What exception does the client throw?

What's the lease duration?  Is the lease expiring prior to the the first 
dirty call?

Does it relate to River-142?


> Is this expected behaviour? Should i bridge the time between the 
> export and the first dirty with a shortlived reference keeper? Should 
> i call dirty on the service side?
> Gr. Sim

View raw message