Unable to synchronize on requestor
SummarySystem slowed down: The Java Virtual Machine (JVM) started collecting the thread dumps after requestor lock exception when the logs were reviewed between 6 AM and 8 AM CT.
Error Messages) ERROR rnbww-dev4572.nam.nsroot.net|SWDTPAVM182113.nam.nsroot.net - SWDTPAVM182113.nam.nsroot.net: com.pega.pegarules.pub.context.RequestorLockException
com.pega.pegarules.pub.context.RequestorLockException: Unable to synchronize on requestor HCA2E286D12F82860113128B46D26438A within 120 seconds: (thisThread = WebContainer : 8) (originally locked by = WebContainer : 2) (finally locked by = WebContainer : 2)
**Date and time**,757 [ WebContainer : 2] [ STANDARD] [ ] [ RUSA:03.15.01] (l.access.ConnectionManagerImpl) ERROR rnbww-dev4572.nam.nsroot.net|wusgtdc-gss02-810.nam.nsroot.net sk62373_dev2 - Not returning connection 8 for database "pegadata" to the pool as it previously encountered the following error
User ID: sk62373_dev2
Last SQL: Alter table RSM_Transaction_View add Zelle Varchar
java.sql.SQLSyntaxErrorException: ORA-00906: missing left parenthesis
Steps to ReproduceUnknown
Root CauseAn issue in the custom application code or rules:
sqlresulttohtml activity is not Pega's out-of-the-box activity and is a custom activity. Any query could be fired according to the User Interface (UI) design, which is handled by sqlresulttohtml activity.
ResolutionUse pagination to obtain the result of the queries if it renders large data to the UI.
Check the custom activity.
Published January 9, 2017 - Updated January 17, 2017