Sizing requestor pools for DXAPI service packages
The system fails while obtaining a requestor from the Requestor pool for the DXAPI Service Package.
...Timed out borrowing service requestor from requestor pool for service package: eapi, timeout set to 10000
...- Resource not found
com.pega.pegarules.pub.PRException: Timed out borrowing service requestor from requestor pool for service package: eapi, timeout set to 10000
at com.pega.pegarules.session.internal.mgmt.RequestorPoolCommonsV2.borrowRequestor(RequestorPoolCommonsV2.java:471) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.RequestorPoolManager.borrowRequestor(RequestorPoolManager.java:153) ~[prprivate.jar:?]
at com.pega.pegarules.integration.engine.internal.services.http.HTTPService.invoke(HTTPService.java:283) ~[printegrint.jar:?]
Steps to Reproduce
A defect or configuration issue in the operating environment.
Here’s the explanation for the reported behavior:
When the project has a growth in the amount of requests through a particular service, the Requestor pool size must be adjusted to accommodate the growth.
The Adjust and Monitor approach is used to increase the Requestor pools in small steps (for example, 20-30-40 requestors). Post this, the growth of concurrent requestors and its impact on the Heap Utilization is monitored.
Published January 16, 2020 - Updated December 2, 2021
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.