felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-4976) Coordinations are always ORPHANED if they only are on the thread stack
Date Thu, 30 Jul 2015 09:44:06 GMT

    [ https://issues.apache.org/jira/browse/FELIX-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647403#comment-14647403

Christian Schneider commented on FELIX-4976:

Do you have some glue code to run the CT ? I did not find anything in the source. I already
got the CT tests. So if you can help me get them running I can debug into the problems and
provide a better fix.

Btw. I wonder if the CoordinationHolder is really necessary. As far as I understood it is
only necessary to allow garbage collection of orphaned coordinations. I wonder if this would
also work if we simply use CoordinationImpl directly and use weak references in CoordinatorImpl
where we do not want to prevent garbage collection.

> 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
>            Assignee: Carsten Ziegeler
>            Priority: Critical
>             Fix For: coordinator-1.0.2
> 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

View raw message