Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Requestor Pool locked



Requestor pool locked errors occur and sessions are not free and requestors are not idle. This occurs with the two services below,

-Delegate Service (Custom application service)
-Monitor (Pega's out-of-the-box service)

Error Messages

Alerts from the Predictive Diagnostic Cloud (PDC):

1. Requestor Pool Locked (RequestorPool-14)
Requestor pool locked for DelegateService

Unable to process a service request for pool / package DelegateService - pool was locked

2. (RequestorPool-1)
Requestor pool locked for monitor

Unable to process a service request for pool / package monitor - pool was locked

Steps to Reproduce

Not Applicable

Root Cause

A defect or configuration issue in the operating environment.
The Requestor pool was full. 
The errors occurred due to authentication. Hence, the requestors were not returned to the pool.


Perform the following local-change:

Ensure that each instance has a separate service account.

Published August 19, 2019 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us