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

High CPU issue and thread dump arpimd RequestorLockExecption



Users see slow interactions with PRPC. The server running PRPC has high CPU usage.

Error Messages

In PegaRULES log:

[<IP Address>] [ ] [ ] [ ] (tent.StaticContentResolverImpl) ERROR - Caught unhandled error in StaticContentResolver handling request aInput = {} doWithRequestorOrThreadLocked could not obtain requestor instance from HEADB79010B7441C2C1941DE814F86C52 

[<IP Address>] [ ] [ ] [ ] (ngineinterface.service.HttpAPI) ERROR <IP Address> - <IP Address>: Unable to synchronize on requestor H3511D492C5A723995CA8F08059199B94 within 120 seconds: (thisThread = http-itgsydsrv231-vip4/ (originally locked by = <IP Address>) (finally locked by = <IP Address>)


Instances of Pega0026.

Steps to Reproduce


Root Cause

The root cause of this problem is a defect in customer application code/rules. An activity was adding rows to the History table and using a Wait action with a date/time in the past.  Because the date is in the past, the loop repeats several times per second, creating a record in the History table each time


Set a date in the future as the target of the Wait action.
Suggest Edit

Published December 11, 2014 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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