river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sim IJskes (JIRA)" <j...@apache.org>
Subject [jira] Commented: (RIVER-331) improve documentation to include the role of AcknowledgmentSource in DGC
Date Mon, 08 Mar 2010 08:51:27 GMT

    [ https://issues.apache.org/jira/browse/RIVER-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842584#action_12842584
] 

Sim IJskes commented on RIVER-331:
----------------------------------

from email:

After export, you get a Proxy with a reference to a BasicInvocationHandler with a reference
to a BasicObjectEndpoint with a reference to a ImplContainer with a reference to your service.

As long as you keep the reference to the exported service, the service is 'strongly reachable'
from the exported service.

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.


> improve documentation to include the role of AcknowledgmentSource in DGC
> ------------------------------------------------------------------------
>
>                 Key: RIVER-331
>                 URL: https://issues.apache.org/jira/browse/RIVER-331
>             Project: River
>          Issue Type: Improvement
>          Components: net_jini_core
>         Environment: documentation
>            Reporter: Sim IJskes
>
> improve documentation to include the role of AcknowledgmentSource in DGC

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message