You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Simon Liang (Jira)" <ji...@apache.org> on 2020/11/26 02:06:00 UTC

[jira] [Created] (IGNITE-13764) NodeJS Thin Client cannot handle multiple concurrent requests

Simon Liang created IGNITE-13764:
------------------------------------

             Summary: NodeJS Thin Client cannot handle multiple concurrent requests
                 Key: IGNITE-13764
                 URL: https://issues.apache.org/jira/browse/IGNITE-13764
             Project: Ignite
          Issue Type: Bug
          Components: thin client
    Affects Versions: 2.9
            Reporter: Simon Liang


When we are using the NodeJS Thin Client, we found that whenever we have multiple requests in-flight, the response ID came out to be mismatched. Upon investigating, I saw that our current response handling is using a blocking loop whenever one data packet arrives, and the subsequent data packet triggers the loop again, causing the response ID mismatch issue.

I have a fix ready on a fork at [https://github.com/lhr0909/ignite/pull/1] and I would like to see if there is a chance to merge in. I use RxJS to handle the packets in full asynchronous fashion.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)