Question
Pegasystems Inc.
US
Last activity: 11 Apr 2016 21:55 EDT
Obj-Save throws an exception
Consistently getting an exception when attaching a document to a case.
obj-save failed. com.pega.pegarules.pub.database.LockGoneException: Save, Delete or Commit has failed because lock "DATA-WORKATTACH-FILE !" is not held
This started happening since we moved to PRPC 7.2. Never seen this in ML 7.1.9.
Any thoughts.
Accepted Solution
Pegasystems
US
You really do need to have the lock. If you think you have it but are still getting this error, do a detailed prpc trace and look for the locking events to understand at what points you are locking and unlocking. /Eric
CGI
US
This is happening in Pega 7.1.8.
I'm confused as to why a lock is needed to do an Obj-Save? "Obj-Save" only does a deferred save (when "Write-Now" is not enabled). I'm assuming only during a "Commit", a lock is necessary.
Here is my scneario:
1. Do Obj-Open-By-Handle with lock and release on commit enabled.
2. This step executes only if step1 is successful. Do an "Obj-Save" WITHOUT "write-now" option.
3.Commit
After step2 above, I'm seeing lot of these LockGoneExceptions after step2 is executed and before step3. I'm not exactly sure what the reason could be. Pega has acquired the lock in step1 and in step2, it says LockGone.
Pegasystems Inc.
US
Is this replicable? Are you sure there are no changes in use cases? If the answers are yes, please create a SR for further investigation.
CGI
US
This is happening in Pega 7.1.8.
I'm confused as to why a lock is needed to do an Obj-Save? "Obj-Save" only does a deferred save (when "Write-Now" is not enabled). I'm assuming only during a "Commit", a lock is necessary.
Here is my scneario:
1. Do Obj-Open-By-Handle with lock and release on commit enabled.
2. This step executes only if step1 is successful. Do an "Obj-Save" WITHOUT "write-now" option.
3.Commit
After step2 above, I'm seeing lot of these LockGoneExceptions after step2 is executed and before step3. I'm not exactly sure what the reason could be. Pega has acquired the lock in step1 and in step2, it says LockGone.
Pegasystems
US
>>> 1. Do Obj-Open-By-Handle with lock and release on commit enabled. 2. This step executes only if step1 is successful. Do an "Obj-Save" WITHOUT "write-now" option. 3.Commit
>>> After step2 above, I'm seeing lot of these LockGoneExceptions after step2 is executed and before step3. I'm not exactly sure what the reason could be
I would think that if you really acquired the lock in step 1, you'd not see the LockGoneException in step 2.
Make sure you do all error-checking at the end of step 1 to make sure you really successfully locked it.
/Eric