Merging a Branch ruleset hangs DEV system
Hello there,
Our entire DEV system hangs while trying to merge a Branch Ruleset with just 5 rules. Even after 30 mins, I see the Pega 7spinning wheel and no developers are able to work when the system hangs.
Every time we have to restart the Tomcat VM when this happens, and see that just 1 or 2 rules merged and rest not merged.
This is happening consistently with the following exception in the log files:
Error Message
com.pega.pegarules.pub.context.RequestorLockException: Unable to synchronize on requestor H621F8137C48F7191B6FCC7B2A2261D5F
within 120 seconds: (thisThread = http-bio-8080-exec-604) (originally locked by = http-bio-8080-exec-609) (finally locked by = http-bio-
8080-exec-609)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.getLockOnRequestor(PRSessionProviderImpl.java:1380)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:915)
Environment
Pega 7.1.4 (CPMFS 7.12)
Tomcat 7
MS SQL Server 2012
I had multiple browser sessions open while merging, does the exception indicate something to do with multiple sessions for my account?
Hello there,
Our entire DEV system hangs while trying to merge a Branch Ruleset with just 5 rules. Even after 30 mins, I see the Pega 7spinning wheel and no developers are able to work when the system hangs.
Every time we have to restart the Tomcat VM when this happens, and see that just 1 or 2 rules merged and rest not merged.
This is happening consistently with the following exception in the log files:
Error Message
com.pega.pegarules.pub.context.RequestorLockException: Unable to synchronize on requestor H621F8137C48F7191B6FCC7B2A2261D5F
within 120 seconds: (thisThread = http-bio-8080-exec-604) (originally locked by = http-bio-8080-exec-609) (finally locked by = http-bio-
8080-exec-609)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.getLockOnRequestor(PRSessionProviderImpl.java:1380)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:915)
Environment
Pega 7.1.4 (CPMFS 7.12)
Tomcat 7
MS SQL Server 2012
I had multiple browser sessions open while merging, does the exception indicate something to do with multiple sessions for my account?
Please advise if you have faced similar issues while merging Branch rulesets, and possible fix.
Pegasystems
US
Unfortunately, the "Unable to synchronize on requestor" message is a general message occurring 120 seconds (2 minutes) AFTER the actual issue occurred that caused the thread to hang, die, or run out of memory.
To get more info, please look back in your log for a previous error that is more specific to the issue.
One thing that might help is, if you know that attempting a branch-merge is causing the issue, look at your log file BEFORE attempting the merge that you know will fail, so that you can see exactly what time stamp is the LAST one in the log file, then perform the ill-fated merge, and carefully examine everything in the log file AFTER the time stamp that WAS noted as the last one before. /Eric
Pegasystems Inc.
IN
Hi Raghu,
Here, you need to find out what this thread, http-bio-8080-exec-609, is actual doing?
There are high chances that this thread is long running and making others wait.
You can also review PegaAlert log to see on what this thread is busy.
Also, kindly share the PegaRULES logs along with PegaALERT for the time when you notice this issue.