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

Async Service Processor creates large number of requestors



When a service is configured with execution mode Asynchronous 'Queue to agent', multiple requestors are created and are never released.

This causes the server to consume large number of resources which will eventually result in a non responsive system.

Error Messages

No error messages but, multiple requestors are visible in System Management Application (SMA) until the server becomes unresponsive.

Steps to Reproduce

  1. Create Service activity (can be blank)
  2. Create Service Request Processor
  3. Create Service Package
  4. Create Service (HTTP) referencing Service Package.
  5. Configure Service rule to reference service activity, set mode of execution to Asynchronous and reference the Service Request Processor.

Root Cause

A defect in Pegasystems’ code or rules.

The Asynchronous mode of execution acquires requestors from the pool while executing the queued jobs but does not return the requestors to pool properly, causing a memory leak.


Apply HFix-34283, and a server restart is needed.

Note: The issue is fixed in Pega 7.2.2.

Published May 24, 2017 - Updated October 8, 2020

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