[
https://issues.apache.org/jira/browse/IGNITE-17249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616271#comment-17616271
]
Roman Puchkovskiy commented on IGNITE-17249:
--------------------------------------------
Thanks!
> 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
> Fix For: 3.0.0-alpha6
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> 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)
