felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FELIX-4976) Coordinations are always ORPHANED if they only are on the thread stack
Date Mon, 03 Aug 2015 19:47:04 GMT

     [ https://issues.apache.org/jira/browse/FELIX-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Carsten Ziegeler resolved FELIX-4976.
-------------------------------------
    Resolution: Won't Fix
      Assignee:     (was: Carsten Ziegeler)

After some discussion in the OSGi EG whether this is a valid case or not, we came to the conclusion
that it's not valid. the implementation should not hold any strong reference, this is the
task of the client code. As in this example no one is holding a strong reference, the coordination
is garbage collected.

> Coordinations are always ORPHANED if they only are on the thread stack
> ----------------------------------------------------------------------
>
>                 Key: FELIX-4976
>                 URL: https://issues.apache.org/jira/browse/FELIX-4976
>             Project: Felix
>          Issue Type: Bug
>          Components: Coordinator Service
>    Affects Versions: coordinator-1.0.0
>            Reporter: Christian Schneider
>            Priority: Critical
>
> The calls below should work but failed as the coordination is regarded as ORPHANED.
> coordinator.begin("test", 0);
> System.gc();
> coordinator.pop().end();
> I can try to provide a fix if you want.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message