E-PRCS: Processes remain Queued on Non-LoadBalanced/Non-Redistributing servers
Last updated on OCTOBER 30, 2017
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.46 to 8.51 [Release 8.4]
Information in this document applies to any platform.
The Master Scheduler does not manage a separate thread for Non-Load Balanced/Non-Redistributing Servers. Instead, there is one thread for process assignment. Processes submitted to a Non-Load Balanced/Non-Redistributing Server must still wait in a Queued status until their proper turn according to a single threaded model.
When a PSJob is submitted and in Processing status to one server, processes submitted to a different server are queued until the first server's processes of the same Process Type are below the Max Concurrent for that Process Type.
For example: PSJob with 30 AEs is submitted to PSNT with MaxConcurrent=5. Simultaneously 1 AE Process is submitted to PSUNX, but this remains queued until only 4 AEs on PSNT remain queued on PSNT. Then the 1 AE submitted to PSUNX initiates. PSUNX has "Do Not LoadBalance" and "Do not Redistribute" so its queue should process separately and should not wait.
* System Load Balancing option is "Assign to Server in Any OS."
* PSUNX Server definition is "Do Not LoadBalance" and "Do not Redistribute".
* Behavior found for AE and SQR Reports.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms