Locks entries present in pr_SysLock table even after WO resolution
Lock entries are still present in lock table even after the WO resolution. These lock entries are causing issues during our agent processing post resolution. Went through the PDN and found there is an issue at product level. But we are witnessing this issue very recently although we are using this system for long time. This issue is happening randomly and not for all cases. Any possibilities for this issue.
PEG
PL
Work-Cover-WorkUnlock is the activity responsible to clear the locks. The logic it follows is simple and you could go through the tracer to figure our what is going wrong there.
In order to further comment, we need to have few details like :
1) parent lock or child lock or both.
2) any customization done.
3) flow
4) prpc version
A simple workaround would be :
1) clear the clear the pr_sys_lock table manually. (i am telling you need to fix this but temporarily this could also be done.)
Best bet :
1. Have a tracer for that work object or scenario and see where it is differing from the correct use case.
Anthem
US
We received a hotfix HFix-27275 for this issue. Root cause is mentioned as below.
In a race condition between FinishAssignment and pyDeleteDocumentPg. When these occur in the wrong order, the system cannot clear the lock.
But it didn't work. We are still following up on this SR. There is no parent-child relation for case. It's happening in CPM.
Updated: 16 Jun 2016 8:20 EDT
Pegasystems Inc.
IN
Unfortunate that you are yet to get a resolution for your issue, I really hope it gets fixed soon. Meanwhile, I would request you to share the SR number details here, so that we can track it for you within the thread.
~Vidyaranjan A V | Community Moderator | Pegasystems Inc.
Pegasystems Inc.
IN
Thank you Srujan for sharing the details.
I see that the SR you are referring to is closed at the moment. For additional assistance with the same issue you will need to reopen the SR using the link provided on the My Support Portal (MSP). Meanwhile, i'll tag the issue description with the SR number for tracking.
Hope the information is helpful.