Sometimes it happens that two consecutive KV*Messages overlap each other and it breaks the Message validation (recognition in the ConcurrentCommunicationService.receive() ) from that point onwards. It results in a deadlock, because neither the server nor the client move forward. (Server didn't recognize the message, client is waiting for the server's response.)
Sometimes it happens that two consecutive KV*Messages overlap each other and it breaks the Message validation (recognition in the ConcurrentCommunicationService.receive() ) from that point onwards. It results in a deadlock, because neither the server nor the client move forward. (Server didn't recognize the message, client is waiting for the server's response.)