SA-1007

Summary

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 = {} 
com.pega.pegarules.pub.PRRuntimeException: doWithRequestorOrThreadLocked could not obtain requestor instance from HEADB79010B7441C2C1941DE814F86C52 

[<IP Address>] [ ] [ ] [ ] (ngineinterface.service.HttpAPI) ERROR <IP Address> - <IP Address>: com.pega.pegarules.pub.context.RequestorLockException 
com.pega.pegarules.pub.context.RequestorLockException: Unable to synchronize on requestor H3511D492C5A723995CA8F08059199B94 within 120 seconds: (thisThread = http-itgsydsrv231-vip4/10.134.155.133:8453-22) (originally locked by = <IP Address>) (finally locked by = <IP Address>)

In PegaRULES-ALERT log:

Instances of Pega0026.
 

Steps to Reproduce

N/A

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

Resolution

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