Skip to main content

I'm submitting a job submisison request to JESControl using the REST client to the following url 

POST "">ip.address.of.server:10086/.../jescontrol"

But my request is getting rate limited and I'm getting the following response:

{
"ErrorTitle" : "Error 429 - Too Many Requests",
"ErrorMessage" : "Session limit has been reached. Please try again later."
}

How do I handle this response. Is the amount to wait before sending the next request is available in any HTTP header ?

Usually when rate-limiting is implemented, the amount of seconds to wait will be available in the 'retry-after' header, however for the above request, I did not see any such header in the response received. So wanted to know if Enterprise Server JESControl is setting this value in any other header or if there is any other way to handle this. 

Thanks for your response. Really appreciate.


#EnterpriseServer

I'm submitting a job submisison request to JESControl using the REST client to the following url 

POST "">ip.address.of.server:10086/.../jescontrol"

But my request is getting rate limited and I'm getting the following response:

{
"ErrorTitle" : "Error 429 - Too Many Requests",
"ErrorMessage" : "Session limit has been reached. Please try again later."
}

How do I handle this response. Is the amount to wait before sending the next request is available in any HTTP header ?

Usually when rate-limiting is implemented, the amount of seconds to wait will be available in the 'retry-after' header, however for the above request, I did not see any such header in the response received. So wanted to know if Enterprise Server JESControl is setting this value in any other header or if there is any other way to handle this. 

Thanks for your response. Really appreciate.


#EnterpriseServer

Hi, I recommend you to consider testing this via the ESCWA docs api page, there you would be able to  see the retry-after option in the header, and gain a better understanding of how to construct/code your request.

The error is a general HTTP message, not specific to the product.


Hi, I recommend you to consider testing this via the ESCWA docs api page, there you would be able to  see the retry-after option in the header, and gain a better understanding of how to construct/code your request.

The error is a general HTTP message, not specific to the product.

Thanks Kim for your response.

  1. The swagger documentation for the api, accessible thru the /docs page only provides the request parameters and the request body. It does not mention the 'retry-after' request header. Can you pls. provide an example http request with this request header. 
  2. We are also trying to understand the business implication of this rate-limiting. Can we relax this rate-limiting by acquiring a different level of license for the product ? 

Thanks again and much appreciate your help.


Thanks Kim for your response.

  1. The swagger documentation for the api, accessible thru the /docs page only provides the request parameters and the request body. It does not mention the 'retry-after' request header. Can you pls. provide an example http request with this request header. 
  2. We are also trying to understand the business implication of this rate-limiting. Can we relax this rate-limiting by acquiring a different level of license for the product ? 

Thanks again and much appreciate your help.

It appears the docs api page does not specifically show the request header information, which tool are you using to execute this, e.g.  a 3rd party tool such as SOAP UI?

For your additional question, that is difficult for me to answer as I am not familiar with your application/requirements. If you need assistance to that please consider to raise a support case and/or let us know if we can arrange consulting, those colleagues will be able to work with you more closely and find an appropriate solution.