You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/11/04 07:24:28 UTC

[jira] [Assigned] (FELIX-5086) Coordinator.begin can return null

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

Carsten Ziegeler reassigned FELIX-5086:
---------------------------------------

    Assignee: Carsten Ziegeler

> Coordinator.begin can return null
> ---------------------------------
>
>                 Key: FELIX-5086
>                 URL: https://issues.apache.org/jira/browse/FELIX-5086
>             Project: Felix
>          Issue Type: Bug
>          Components: Coordinator Service
>    Affects Versions: coordinator-1.0.0
>            Reporter: Eduard Vodicka
>            Assignee: Carsten Ziegeler
>            Priority: Critical
>             Fix For: coordinator-1.0.2
>
>         Attachments: Fix_null_return.patch, test_to_demonstrate_GC_problems.patch
>
>
> Calls to CoordinatorImpl.begin (and CorrdinatorImpl.create) can return null, if the Garbage Collector runs between the creation of the Coordination and the return of the CoordinationHolder reference.
> During that time, only the WeakReference to the Holder exists, therefor it is removed and cannot be returned to the caller.
> This can easily happen in high load scenarios with many calls to CoordinatorImpl.begin. The caller has no chance of ever receiving a Coordination reference.
> I created a simple test do demonstrate the problem.



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