Error Message :
It is a known issue that allowing the Backlog to grow to 3,000 or more Jobs can cause performance degradation. This will result in the one or more, but not limited to the following behaviors:
- Jobs stuck in QUEUED status
- Slow Job status changes
- Finished Jobs are delayed to drop into History
- Slowness in overall Java Web Client refresh
- Jobs not processing
- A continued increase in backlog count
- Awapi times out during startup
- Inability to launch the Java Web Client
Applications Manager is a 32-bit single threaded application that only has a limited number of Java threads that can be used for database/agent communication, sub-var resolution, Job scheduling/status updates, condition handling, Java Web Client refreshes, etc.
It is highly recommended to avoid any situation where thousands of Jobs are immediately scheduled into the Backlog or to allow the Backlog to grow to 3,000 or more Jobs. Doing so will use up all available Java threads causing one or more of the above symptoms.NOTE:
Keep in mind that the 3000 Job threshold is ONLY an estimate. This number can vary greatly depending on hardware, network, and database performance as well as types of Jobs in the Backlog.