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

Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2022/09/30 13:40:00 UTC

[jira] [Assigned] (IGNITE-17249) DefaultMessagingService incorrect message sending order

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

Roman Puchkovskiy reassigned IGNITE-17249:
------------------------------------------

    Assignee: Roman Puchkovskiy

> DefaultMessagingService incorrect message sending order
> -------------------------------------------------------
>
>                 Key: IGNITE-17249
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17249
>             Project: Ignite
>          Issue Type: Bug
>          Components: networking
>            Reporter: Semyon Danilov
>            Assignee: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>
> The issue is in the 
> {{private CompletableFuture<Void> sendMessage0(NetworkMessage message, String recipientConsistentId, InetSocketAddress addr)}} method.
> {{connectionManager.channel(recipientConsistentId, addr)}} returns a future and we add a "listener" via {{thenCompose}} method. The thing is that it adds a listener to the start of the queue, so when the channel is established the latest listener will be executed first.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)