2.4 should be OK. What you showed that the stream receiver called invoke() and did not get an answer, not a deadlock. Nothing looks particularly wrong there. When we created this bug, it was our a stream receiver called invoke() and that in turn did another invoke, which was the actual bug.
It was helpful when we did the invoke using a custom thread pool, because the logging reports thread in the custom pool, we could see which node had active custom threads easily, and then look at what that thread was waiting for. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
