[
https://issues.apache.org/jira/browse/IGNITE-17656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17602279#comment-17602279
]
Ignite TC Bot commented on IGNITE-17656:
----------------------------------------
{panel:title=Branch: [pull/10241/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10241/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6599204&buildTypeId=IgniteTests24Java8_RunAll]
> Race in DistributedProcess#onSingleNodeMessageReceived
> ------------------------------------------------------
>
> Key: IGNITE-17656
> URL: https://issues.apache.org/jira/browse/IGNITE-17656
> Project: Ignite
> Issue Type: Bug
> Reporter: Maksim Timonin
> Assignee: Maksim Timonin
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> DistributedProcess#onSingleNodeMessageReceived
> It could be a case when 2 (one of them is the last) messages receives
> simultaneously:
> # Initial state: remaining = \{node0, node1}, singleMsg={}
> # First msg handled, thread stops after releasing the `mux`:
> remaining=\{node0}, singleMsg={}.
> # Second msg handled, thread doesn't stop and: remaining={},
> singleMsg=\{node1}. And finishes process after that.
> # Thread 1 invoked, put message to singleMsg, but process was already
> finished.
>
> Solution is changing both collections (remaining, singleMsg) under the same
> `mux`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
