You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by "Dmitry Karachentsev (JIRA)" <ji...@apache.org> on 2017/02/22 07:15:44 UTC

[jira] [Created] (IGNITE-4740) Service could be initialized twice on concurrent cancel and discovery event

Dmitry Karachentsev created IGNITE-4740:
-------------------------------------------

             Summary: Service could be initialized twice on concurrent cancel and discovery event
                 Key: IGNITE-4740
                 URL: https://issues.apache.org/jira/browse/IGNITE-4740
             Project: Ignite
          Issue Type: Bug
          Components: managed services
    Affects Versions: 1.8
            Reporter: Dmitry Karachentsev
            Assignee: Dmitry Karachentsev
             Fix For: 2.0


In case of concurrent service cancel and discovery event, for example, applying continuous query, may cause double init() and execute() service method invocation.

Fix should consist at least in filtering such DiscoveryCustomEvent in GridServiceProcessor.TopologyListener.
The best solution is guarantee that despite of any discovery event service won't be intialized more than once.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)