[
https://issues.apache.org/jira/browse/IGNITE-13827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17245722#comment-17245722
]
Aleksey Plekhanov commented on IGNITE-13827:
--------------------------------------------
Root cause: task result returned to thin-client with notification, these
notifications processed by receive thread, including result unmarshalling.
During unmarshalling client founds an unknown type, send a type request to the
server, and wait for a response, but the response can't be read by the receive
thread, because the receive thread still waits for the sync type request.
To avoid hangs on unknown types we should process notifications in another
thread.
> Deadlock when receiving ComputeTask result by IgniteClient.
> -----------------------------------------------------------
>
> Key: IGNITE-13827
> URL: https://issues.apache.org/jira/browse/IGNITE-13827
> Project: Ignite
> Issue Type: Bug
> Components: thin client
> Reporter: Sergei Ryzhov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Deadlock when receiving ComputeTask result by IgniteClient.
> when ComputeTask return a user object for example:
> {code:java}
> class TestVal(){
> String val;
> }
> {code}
> WA client.binary().toBinary(new TestVal());
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
