Is API Action on Server Action on NodeJS using HTTP/2 or Keep-Alive to allow performing several successive requests (e.g.: inside a Repeat step) with minimal performance penalty/to avoid successive closing-and-opening TCP connections when contacting external services/APIs?
1 Like
You received a response?
I haven't
Maybe you could setup a mock URL on Beeceptor and see if the captured request header has Keep-Alive in there
Understood, I have several problems every day with this API action. My system is large and has high requests per second. I configured the "while action" for a new attempt with an exponential strategy. Wappler applies the strategy, but fails in several other requests, and the receiving system never refuses connections.
Search about "open file limit"
I researched this a while ago, the service that receives requests is a banking service. The load we accept is 300rps. In other words, it is very sophisticated. Overall, the Action API facing issues. I just tested the 'Connection' header with 'keep-alive' and it didn't work. I guess I had to build an API extension to surprise this. I contacted the bank and the same staff informed that only my company faces this problem. @patrick How to solve this problem without need create a custom "API Action" for save connections internaly?