Issue
In Riva Cloud or Riva On-Premise, "(503) Server Unavailable" errors may sporadically appear throughout crmex-log files.
2011-11-22 10:06:17,054 ERROR [CTP-jwc #814] [909838433] Minor error occurred during synchronization.
Omni.Scheduling.SchedulePostponeException: The remote server returned an error: (503) Server Unavailable. ---> System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
Omni.Scheduling.SchedulePostponeException: The remote server returned an error: (503) Server Unavailable. ---> System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
Cause
Oracle CRM On Demand imposes a set of "web services on demand limiters" that can limit
- the total number of concurrent requests for data,
- the maximum values for records, and
- the volume of data requested.
If the total volume of data being requested or synced during a Riva sync cycle exceeds the permitted threshold value, Oracle On Demand web services report that the server is unavailable.
Solution
- If this issue is a low occurrence error, it can be safely ignored.
- If the issue becomes pronounced, adjustments need to be made to reduce the number of requests and volume of data syncing.
Solution for Riva Cloud
Solution for Riva On-Premise
Reducing the number of requests and/or volume of data syncing can be accomplished in several ways, including:
- Reducing the number of concurrent execution threads that Riva is using. This will reduce the number of requests and volume of data. For more information, see Controlling concurrent Riva synchronization threads.
- If users are syncing large attachments, you could
- go as far as disabling attachments on a per-module basis, or
- (less radically) implement attachment size limits: for more information, see the "configure attachment options" section of