You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2015/09/09 12:33:45 UTC
[jira] [Closed] (IGNITE-1391) Platform .Net: Messaging.RemoteListen
causes deadlock when remote node interop is initializing
[ https://issues.apache.org/jira/browse/IGNITE-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov closed IGNITE-1391.
-----------------------------------
> Platform .Net: Messaging.RemoteListen causes deadlock when remote node interop is initializing
> ----------------------------------------------------------------------------------------------
>
> Key: IGNITE-1391
> URL: https://issues.apache.org/jira/browse/IGNITE-1391
> Project: Ignite
> Issue Type: Bug
> Components: interop
> Affects Versions: 1.1.4
> Reporter: Pavel Tupitsyn
> Assignee: Vladimir Ozerov
> Priority: Critical
> Fix For: ignite-1.4
>
>
> * when node joins the topology, interop processor is not yet ready (Ignite instance is not created in .Net)
> * When that node receives a remote message listener, UnmanagedCallbacks.MessagingFilterCreate gets called, and it blocks on "_initEvent.Wait()"
> * This blocks whole messaging mechanism, so interop processor initialization can't be completed
> We need to:
> * Override onKernalStart in PlatformProcessorImpl and call platform.onStart from there
> * In .Net, release _initEvent from that callback
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)