Deal with MS_MAX_CONCURRENT_REQ by re-trying with exponential back-off? #79
Description
there is a limitation on the concurrent requests handled by VoW. There is a maximum number of concurrent requests the system can handle. If the system receives a new request and the maximum number of concurrent requests is reached, the request is rejected. The maximum number of concurrent requests is not linked to a specific IP. It is a global count across all users. In addition, the MAX Concurrent limitations addresses both the VoW overall as well as each Member State separately and for each type of validation request namely, Manual (INT), SOAP (API), REST (API) as well as BATCH. On request though from some National Administrations, we unfortunately cannot disclose the exact level of the thresholds in VoW.
Since we keep running into this issue and it can be circumvented by retrying at increasing intervals, should we handle this from within the library?