Question
Pegasystems Inc.
US
Last activity: 17 Jul 2017 11:22 EDT
Users seeing unable to synchronize on requestor when trying to login
When the users are trying to login to the application, they receive the below error on the screen. The same error appears in application logs.
Unable to synchronize on requestor HF103F32660B65612FF70E19D14F5EF75 within 120 seconds: (thisThread = http-bio-8181-exec-34) (originally locked by = http-bio-8181-exec-59) (finally locked by = http-bio-8181-exec-59)
ERROR MESSAGES
02:34:50,692 [p-bio-8181-exec-3084] (ngineinterface.service.HttpAPI) ERROR - <IP Address>: com.pega.pegarules.pub.context.RequestorLockException
com.pega.pegarules.pub.context.RequestorLockException: Unable to synchronize on requestor H6B6CC0E416B6880CCDE6CC1C7E45EB6E within 120 seconds: (thisThread = http-bio-8181-exec-3084) (originally locked by = http-bio-8181-exec-3115) (finally locked by = http-bio-8181-exec-3115)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1000)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:792)
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequest(EngineAPI.java:328)
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.invoke(HttpAPI.java:717)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:312)
When the users are trying to login to the application, they receive the below error on the screen. The same error appears in application logs.
Unable to synchronize on requestor HF103F32660B65612FF70E19D14F5EF75 within 120 seconds: (thisThread = http-bio-8181-exec-34) (originally locked by = http-bio-8181-exec-59) (finally locked by = http-bio-8181-exec-59)
ERROR MESSAGES
02:34:50,692 [p-bio-8181-exec-3084] (ngineinterface.service.HttpAPI) ERROR - <IP Address>: com.pega.pegarules.pub.context.RequestorLockException
com.pega.pegarules.pub.context.RequestorLockException: Unable to synchronize on requestor H6B6CC0E416B6880CCDE6CC1C7E45EB6E within 120 seconds: (thisThread = http-bio-8181-exec-3084) (originally locked by = http-bio-8181-exec-3115) (finally locked by = http-bio-8181-exec-3115)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1000)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:792)
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequest(EngineAPI.java:328)
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.invoke(HttpAPI.java:717)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:312)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:263)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:240)
at com.pega.pegarules.priv.context.JNDIEnvironment.invokeEngineInner(JNDIEnvironment.java:277)
at com.pega.pegarules.priv.context.JNDIEnvironment.invokeEngine(JNDIEnvironment.java:222)
at com.pega.pegarules.web.impl.WebStandardImpl.makeEtierRequest(WebStandardImpl.java:383)
at com.pega.pegarules.web.impl.WebStandardImpl.doPost(WebStandardImpl.java:271)
at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
***Updated by moderator: Lochan to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Looks like you have a slow database - the thread dump suggests DB read is taking a long time to complete. Involve your DBA to fine tune the DB read performance.
java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1525)
at com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:3274)
Your PRPC application might also be suffering from a known issue around StringPoolSet module. Open up a SR with GCS for investigation in this regard.
Accepted Solution
Looks like you have a slow database - the thread dump suggests DB read is taking a long time to complete. Involve your DBA to fine tune the DB read performance.
java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1525)
at com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:3274)
Your PRPC application might also be suffering from a known issue around StringPoolSet module. Open up a SR with GCS for investigation in this regard.
BNY Mellon
US
I'll add here, even after a Answer has been marked "Correct", that this is a common problem across multiple versions that needs common explanation.
As per PDN, this goes back at least to v5.1 (2007) and likely before.
https://pdn.pega.com/system-operations/troubleshooting-unable-to-synchronize-on-requestor-timeout-after-120-seconds
This is often a message that gets displayed to users, and there could be any number of reasons.
It'd be helpful (worth a separate thread) to go through the standard user errors, and provide a simple error code, along with configurable message containing an explanation and direction ("The server is experiencing high loads; please try your request again in a few minutes. If issues continue, please contact your adminstration.")
The PDN article above should probably be updated as well,
I'll add here, even after a Answer has been marked "Correct", that this is a common problem across multiple versions that needs common explanation.
As per PDN, this goes back at least to v5.1 (2007) and likely before.
https://pdn.pega.com/system-operations/troubleshooting-unable-to-synchronize-on-requestor-timeout-after-120-seconds
This is often a message that gets displayed to users, and there could be any number of reasons.
It'd be helpful (worth a separate thread) to go through the standard user errors, and provide a simple error code, along with configurable message containing an explanation and direction ("The server is experiencing high loads; please try your request again in a few minutes. If issues continue, please contact your adminstration.")
The PDN article above should probably be updated as well,
"In most cases you can ignore this error, as the situation is temporary and transient. If the error continues to occur and hinders production, you need to explore why this is occurring. A simple solution to the requestor timeout issue is to clear your browser cache, thus issuing a new request to free up resources to attempt to complete the task."
We don't want to tell our users to clear their browser cache if it's not likely to solve the problem.
AIG
US
"Unable to synchronize on requestor H4733C449EBB0C1825910F4CF3805427F within 120 seconds" -
1) Where is this "120 Seconds" value set and what's the parameter name?
2) What if there's a genuine requirement where the processing takes more than 120 Seconds?