SA-12724

Summary

Configured AES 3.4 to monitor PRPC 6.1 SP2. an error is received when searching for Agents from AES Enterprise Health portal screen. The monitored node is correctly detected.

Error Messages

Caught unexpected com.pega.pegarules.pub.PRRuntimeException, message='Problem obtaining requestor from ServiceRequestorPool

Steps to Reproduce

Not Applicable

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules. 

Resolution

This issue is resolved through the following local-change:

Modify PEGAAES Service Package on AES Server to:

    Maximum Idle Requestor - 50
    Maximum Active Requestor - 100
    Maximum Wait (in seconds) - 25

AND

PEGAAESREMOTE Service Package on 6.1 SP2 to:

    Maximum Idle Requestor - 25
    Maximum Active Requestor - 50
    Maximum Wait (in seconds) - 20