We have a scenario in @cap-js/hana that a blob column is streamed out of the database and is being inserted into a different table. When doing this the Queue.js implementation creates a dead lock. As the lob read request cannot be send while actively processing the insert statement.
This PR solves this limitation by removing the Queue.js from the connection. Instead using the packetCount to identify what callback to use when a response is received from the the HANA system.
There is still a pseudo queue in the current implementation as simply sending the request to the system without waiting for an acknowledgement. Results in sporadic connection terminations by the HANA system. With the reason invalid packet length while sending the exact same packets.
We have a scenario in
@cap-js/hanathat a blob column is streamed out of the database and is being inserted into a different table. When doing this theQueue.jsimplementation creates a dead lock. As the lob read request cannot be send while actively processing the insert statement.This PR solves this limitation by removing the
Queue.jsfrom the connection. Instead using thepacketCountto identify what callback to use when a response is received from the the HANA system.There is still a pseudo queue in the current implementation as simply sending the request to the system without waiting for an acknowledgement. Results in sporadic connection terminations by the HANA system. With the reason
invalid packet lengthwhile sending the exact same packets.