Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

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.

Understanding requestor pools

Updated on April 5, 2022

  • Clearing a requestor pool

    You can terminate requestors for a pool on a given node or on all nodes in the cluster by clearing a requestor pool. This action clears all requestor IDs and resets the requestor count to zero for the selected service package. Clearing the requestor pool is used for tuning purposes and can help you efficiently manage system resources. For example, if too many requests wait for a requestor to return to the pool for a long time, you can clear the pool to release the requestors.

  • Viewing details for a listener

    You can view more details about any listener across the cluster, such as listener name, class, and ID, the number of requests and errors that occurred, the state and status of a listener, the node on which a listener is running, and the time when a listener was started.

Have a question? Get answers now.

Visit the Support 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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us