[IGNITE-13764] NodeJS Thin Client cannot handle multiple concurrent requests

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 2.9
• Component/s: thin client
• Flags: Patch
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: Simon Liang
• Reviewer: Igor Sapego
• Created: 26/Nov/20 02:05
• Updated: 26/Nov/20 02:05

Description

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.