Understanding ProcessServiceQueue schedules
All service requests are being processed asynchronously (Queue on error) to handle the case locking issues , but how do we configure an interval for each iteration
The Maximum number of execution attempt is configured as 3 in Service Request Processor data instance but all three attempts are happening within a minute even through OOTB ProcessServiceQueue agent is configured to execute for 5 mins and running in only one node .
<rowdata REPEATINGINDEX="1"> <pxObjClass>Embed-QueueErrorDetails</pxObjClass> <pxErrorMessage>Fail Cannot obtain a lock on instance myorg-app-work L-XXXXXX, as Requestor HN5KQPIYU3JIADC2MZL6D8B5PI3R0HISRA already has the lock</pxErrorMessage> <pxErrorDateTime>20200220T123943.606 GMT</pxErrorDateTime> <pyAttempt>1</pyAttempt> <pxTraceList>[]</pxTraceList> <pxAuthDetails>
rowdata REPEATINGINDEX="2"> <pxObjClass>Embed-QueueErrorDetails</pxObjClass> <pxErrorMessage>Fail Cannot obtain a lock on instance myorg-app-work L-XXXXXX, as Requestor HN5KQPIYU3JIADC2MZL6D8B5PI3R0HISRA already has the lock</pxErrorMessage> <pxErrorDateTime>20200220T123944.403 GMT</pxErrorDateTime> <pyAttempt>2</pyAttempt>
All service requests are being processed asynchronously (Queue on error) to handle the case locking issues , but how do we configure an interval for each iteration
The Maximum number of execution attempt is configured as 3 in Service Request Processor data instance but all three attempts are happening within a minute even through OOTB ProcessServiceQueue agent is configured to execute for 5 mins and running in only one node .
<rowdata REPEATINGINDEX="1"> <pxObjClass>Embed-QueueErrorDetails</pxObjClass> <pxErrorMessage>Fail Cannot obtain a lock on instance myorg-app-work L-XXXXXX, as Requestor HN5KQPIYU3JIADC2MZL6D8B5PI3R0HISRA already has the lock</pxErrorMessage> <pxErrorDateTime>20200220T123943.606 GMT</pxErrorDateTime> <pyAttempt>1</pyAttempt> <pxTraceList>[]</pxTraceList> <pxAuthDetails>
rowdata REPEATINGINDEX="2"> <pxObjClass>Embed-QueueErrorDetails</pxObjClass> <pxErrorMessage>Fail Cannot obtain a lock on instance myorg-app-work L-XXXXXX, as Requestor HN5KQPIYU3JIADC2MZL6D8B5PI3R0HISRA already has the lock</pxErrorMessage> <pxErrorDateTime>20200220T123944.403 GMT</pxErrorDateTime> <pyAttempt>2</pyAttempt>
<rowdata REPEATINGINDEX="3"> <pxObjClass>Embed-QueueErrorDetails</pxObjClass> <pxErrorMessage>Fail Cannot obtain a lock on instance myorg-app-work L-XXXXXX, as Requestor HN5KQPIYU3JIADC2MZL6D8B5PI3R0HISRA already has the lock</pxErrorMessage> <pxErrorDateTime>20200220T123945.196 GMT
***Edited by Moderator Marissa to update platform capability tags; update SR Details****
Updated: 21 Mar 2020 21:53 EDT
Pegasystems Inc.
IN
Hi,
I hope you can enable the agent to run only on one node then enable delay next run and provide the interval value.
Thank You,
Skandiabanken
SE
where can i find the vale for delay factor ? Is there any DSS for this configuration in 7.3.1?
ProcessServiceQueue advanced agent is running for every 180 sec .
When i looked at xml of the service queue instance, i could see only pyMinimumDateTimeForProcessing and no value for pyMinimumAgeForProcessing .
we would like to know ,how pyMinimumDateTimeForProcessing is being calculated for Service queue instances .
Pegasystems Inc.
US
Hello,
It would be helpful to have a bit more context. When you say "All service requests are being processed asynchronously (Queue on error) to handle the case locking issues" what do you mean. Are you saying you have a flow that when it gets a locking issue, it sends it off to a queue? If so, can you go into how you are configuring this? Screen shots might help. If you are saying that all work is being done asynchronously, occasionally you run into locking errors, it would be helpful to understand this as well. Do you know what has the lock?
I realize your question is around the requeuing. Again, it would be helpful to see a screen shot or two so we know what you have configured and are all starting from the same place.
Thanks, Mike
Skandiabanken
SE
Thanks Mike for esponse ..
we have multiple services/API's exposed to external system , One of the pega service should able to cancel a case in pega . In the service activity ,we are trying to open a case (case id comes in request from external system) and if case is being locked in pega portal during the time service request comes in then we need to queue the service request(cancel) and process the cancel request when it gets lock on the case .
To achieve this we used OOTB ProcessServiceQeueue and encountered issue is ,The Maximum number of execution attempt is configured as 3 in Service Request Processor data instance but all three attempts are happening within a minute even through OOTB ProcessServiceQueue agent is configured to execute for 5 mins and running in only one node .
However , it's bug in pega platform (https://community.pega.com/support/support-articles/pega-intsvcs-agent-does-not-work-correctly).. we had received the new hotfix for 7.3.1
Skandiabanken
SE
Thanks Mike for response ..
we have multiple services/API's exposed to external system , One of the pega service should able to cancel a case in pega . In the service activity ,we are trying to open a case (case id comes in request from external system) and if case is being locked in pega portal during the time service request comes in then we need to queue the service request(cancel) and process the cancel request when it gets lock on the case .
To achieve this we used OOTB ProcessServiceQeueue and encountered issue is ,The Maximum number of execution attempt is configured as 3 in Service Request Processor data instance but all three attempts are happening within a minute even through OOTB ProcessServiceQueue agent is configured to execute for 5 mins and running in only one node .
However , it's bug in pega platform (https://community.pega.com/support/support-articles/pega-intsvcs-agent-does-not-work-correctly).. we had received the new hotfix for 7.3.1