on Apr 30, 2019Article Content
| Article Number | 000037375 |
| Applies To | RSA Product Set: RSA Archer RSA Version/Condition: 6.5 and greater |
| Issue | Under-utilization of job threads is observed due to the Max Thread Per Job Type setting when the job queue is filled with jobs of few types. |
| Cause | When the Max Thread Per Job Type setting is enabled in the Archer Control Panel under the Servers tab of the Job Engine Manager, the job engine ensures that the total number of jobs for any specific job-type does not cross the limit set by this configuration. It can cause an adverse effect when the total number of jobs in the job queue is limited to a few types, which is less than the total number of threads available. The Job Engine does not process more jobs beyond the Max Thread Per Job Type setting under any circumstance. Example Scenario for Illustration of the issue only 
|
| Resolution | The Max Thread Per Job Type setting is introduced to avoid starvation to low priority jobs due to the high number of high priority jobs. The setting gives best result when the job engine is under load with a high number of high priority jobs which results in the low priority to remain in the queue for a long time (or forever). Enable the Max Thread Per Job Type after careful analysis of the job engine performance and job execution patterns. |