Support Article
Optimistic locking in Pega 7.1.9 - Open items not being updated.
SA-19987
Summary
Optimistic locking is not working in Pega 7.1.9 for the below scenario after upgrade from 7.1.7:
Case structure:
'Site' is the top case with the child case 'Booking'.
At run-time, the Booking case receives SOAP calls externally and it should update work object data. When the work object is found to be open by any operator, the update is not happening.
This used to work before upgrade to Pega 7.1.9. We upgraded to the new environment last weekend.
We notice that the Booking case (child case) has Locking set to 'A Case is Opened' option in pyDefault case type rule.
In spite of multiple check-ins after resetting to a different value, this is set back to this value.
Error Messages
No errors in UI but lock not available exception in the log files.
Steps to Reproduce
Simulate an external SOAP call by keeping the WORK OBJECT open and the SOAP call will fail when it tries to acquire a work object lock.
Root Cause
A defect or configuration issue in the operating environment.
During the pega platform upgrade from 7.1.7 to 7.1.9 somehow the parent case locking strategy got reset back to 'A case is opened' which got inherited by its child case.
Resolution
Perform the following local-change:
Set the correct locking strategy and now the child case instances are working as expected.
Published February 18, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.