You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/10/08 08:55:00 UTC

[jira] [Commented] (IGNITE-9742) Illegal change of DiscoveryCustomEvent in GridDhtPartitionsExchangeFuture#onDone

    [ https://issues.apache.org/jira/browse/IGNITE-9742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16641549#comment-16641549 ] 

ASF GitHub Bot commented on IGNITE-9742:
----------------------------------------

Github user daradurvs closed the pull request at:

    https://github.com/apache/ignite/pull/4875


> Illegal change of DiscoveryCustomEvent in GridDhtPartitionsExchangeFuture#onDone
> --------------------------------------------------------------------------------
>
>                 Key: IGNITE-9742
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9742
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.6
>            Reporter: Vyacheslav Daradur
>            Assignee: Vyacheslav Daradur
>            Priority: Major
>              Labels: discovery
>             Fix For: 2.8
>
>
> The following code is called in {{GridDhtPartitionsExchangeFuture#onDone}}:
> {code}
> ((DiscoveryCustomEvent)firstDiscoEvt).customMessage(null);
> {code}
> That means a global instance of 'DiscoveryCustomEvent' is being
> mutated outside discovery-spi infrastructure. It also means that
> discovery listeners receive 'DiscoveryCustomEvent' with 'null' field
> instead of 'CustomMessage' which they may rely on.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)