All of my requests being sent via RESTful API that previously worked have recently been receiving a 429 HTTP status code indicating too many requests have been sent to the API.
I'm getting the following response:
{ "ErrorTitle" : "Error 429 - Too Many Requests", "ErrorMessage" : "Session limit has been reached. Please try again later." }
The error is a general HTTP message, not specific to the product.
How do I mitigate this obstacle? What is the admin configuration setting in the Enterprise Server to extend the session limit and relax the rate-limiting?
The Retry-After header is an HTTP response header that informs the client how long it should wait before making another request is commonly used in scenarios where the server cannot process the request immediately, such as rate-limiting or scheduled downtime. I do not want any of the rate-limiting or scheduled downtime that I’m currently experiencing.
Best answer by Bruce Cheatwood
The issue is that the number of open sessions has exceeded the maximum allowed not an influx of the number of requests in a given time. We have temporarily mitigated the issue by increasing the maximum number of allowed sessions.
Although, the permanent solution would be to somehow clear the existing sessions so that the maximum is never reached. This may be able to be solved by decreasing the session timeout. It seems that the default session timeout is 20 days for some reason which is absurdly long and has likely caused this issue.
How to change the maximum number of allowed sessions and session timeout:
Navigate to the Enterprise Server Common Web Administration (ESCWA) tool used to administer the server.
Click the gear icon on the top right to navigate to the Enterprise Server Configuration popup.
The issue is that the number of open sessions has exceeded the maximum allowed not an influx of the number of requests in a given time. We have temporarily mitigated the issue by increasing the maximum number of allowed sessions.
Although, the permanent solution would be to somehow clear the existing sessions so that the maximum is never reached. This may be able to be solved by decreasing the session timeout. It seems that the default session timeout is 20 days for some reason which is absurdly long and has likely caused this issue.
How to change the maximum number of allowed sessions and session timeout:
Navigate to the Enterprise Server Common Web Administration (ESCWA) tool used to administer the server.
Click the gear icon on the top right to navigate to the Enterprise Server Configuration popup.
