Question
System is behaving slow because of Thread dump genearted by the below error
Can anyone please suggest what could be the reasons for below error and what can be done to avoid this
ERROR com.pega.pegarules.pub.context.RequestorLockException
com.pega.pegarules.pub.context.RequestorLockException: Unable to synchronize on requestor
Hi Shanthini,
PRPC version used here is 6.2 and the user count will be around 40. Due to the thread dumps system slowness and exceptions are being experienced.
So is there any way we can avoid this ?
Thanks & Regards
Ravi
Hi Ravikiran,
Can you provide the log files? Seeing the requestor lock exception and thread dump that preceeded it will help to pinpoint what the problem is.
Thanks,
Brad
Hi Ravi,
Unable to synchronize on requestor occurs when a thread at JVM level is not able to acquire lock on it.
How to debug this:-
1) Open the log file and locate the unable to synchronize message
2)There will be thread name related to this which will be mentioned as finally locked by.
3) Scroll up to the thread dumps and locate the thread found in step 2 with runnable status.
4) Check what the thread is doing to understand the root cause.
In most of the cases it would be DB being on the slower side.
Thanks,
Ujjwal
Hello Ravikiran,
Due to the thread dump you need frequent restarts of the server? Can you confirm how many users are using it simultaneously? Confirm the PRPC version.
In the past we have seen some known issues in 7.1.8. You can refer : https://pdn.pega.com/support-articles/server-slow-post-sandbox-upgrade-pega-718.
Regards,
Shanthini Charles