Support Article
Bulk Transfer functionality is not working properly
SA-23454
Summary
When transferring more than 30 cases from one workbasket to other workbasket with "Run in Background" checked, developer is getting LockGoneException. It appears that the cases are running in the background but not going to the directed destination. They are just running in the background and then reappearing in the original workbasket.
Error Messages
com.pega.pegarules.pub.database.LockGoneException: Save, Delete or Commit has failed because lock "X-X-X" is not held
at com.pega.pegarules.data.internal.access.LockManagerImpl.checkRequiredLocks(LockManagerImpl.java:1090)
at com.pega.pegarules.data.internal.access.DatabaseImpl.checkRequiredLocks(DatabaseImpl.java:2189)
at com.pega.pegarules.data.internal.access.DatabaseImpl.attemptToProcessUpdates(DatabaseImpl.java:2392)
at com.pega.pegarules.data.internal.access.DatabaseImpl.processUpdates(DatabaseImpl.java:2231)
at com.pega.pegarules.data.internal.access.DatabaseImpl.commit(DatabaseImpl.java:1971)
Steps to Reproduce
Transfer multiple cases from one workbasket to another workbasket.
Root Cause
There is a custom activity which performs "Obj-Save" to attach a note to the work object. Generally the above error message is because, Obj-save methods requires a lock to save any instance.
Resolution
Include a step which performs "Obj-Refresh-Lock" before "Obj-Save" which makes sure that the lock is held on the Work Object before writing it to the database.
Published May 25, 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.