Best Practices
Take a closer look at when concurrency peaks happen and consider rescheduling requests to avoid peak times.
Make sure your client applications are designed to handle error codes properly. The following example shows how to handle error codes programmatically:
int i = 0;
int maxAttempts = 5; // try it 5 times, then fail for good
while (i < maxAttempts)
{
response = doWSCall();
isSuccess = response.getIsSuccess();
errorMsg = response.getErrorMsg();
if (isSuccess == false && (errorMsg == WS_CONCUR_SESSION_DISALLWD || errorMsg == WS_REQUEST_BLOCKED))
{
wait();
i++; // try again
}
else
{
break; // end the cycle
}
}
Upgrade your client applications to serialize requests and prevent overlap between non-concurrent users.
pdating your SOAP web services integrations to use Token-Based Authentication (TBA) allows for more flexible concurrency.
Related Topics
- Web Services and RESTlet Concurrency Governance
- Concurrency Governance Limits Based on Service Tiers and SuiteCloud Plus Licenses
- Concurrency Governance for Internal Applications
- Effects of Authentication Method on Concurrency Governance
- Account Concurrency Monitoring Resources
- Errors Related to Concurrency Violations
- Retrying Failed Web Services Requests
- Sample Scenario
- Frequently Asked Questions