Oracle Web Services On Demand Guide > Web Services On Demand Limiters >

Web Services Request Rate

All integration requests (data exchange requests) in a session are subject to rate limiting. Rate limiting is implemented for the following reasons:

• A user can perform long-running operations on the server that result in complex and long-running queries on the database.
• A user can perform constant operations on the server that constantly use resources.

Rate limiting can alleviate the previous problems to some extent. Oracle CRM On Demand applies a restriction to each session to limit the number of requests for each second that clients can make. The rate limit is set to twenty requests for each second. This is measured as a minimum of 1/20th second wait time between requests.

If the rate limit is exceeded, the following error message is provided to subsequent SOAP requests:

The maximum rate of requests was exceeded. Please try again in <waitTime> ms.

There are two situations in which this error message is displayed:

• Where the client sends more than 20 requests every second
• Where the client sends requests at a rate faster than one request every 50 milliseconds.

For the second situation, a wait statement is recommended.