SA-69277

Summary

Sporadic LockGoneExceptions are seen after syncing a device that has been offline.

Error Messages

Commit;RULE-OBJ-ACTIVITY WORK- PYMOBILESYNCSAVEWITHERRORS #20160405T152159.823 GMT Step: 2 Circum: 0;doActivity Rule-Obj-Activity:pyMobileSyncSaveWithErrors;java;RULE-OBJ-ACTIVITY @BASECLASS PZSTOREANDFORWARDPROCESSITEMS #20160707T080543.319 GMT Step: 4 Circum: 0;14 additional frames in stack;*pzRowIndex=1;*[MSG][Error in commit()][STACK][com.pega.pegarules.pub.database.LockGoneException: Save, Delete or Commit has failed because lock "...-WORK " is not heldFrom: (AB68C3EE3AB375E9156E8A7DECB55FC2F) SQL: select pxOwnerId as "pxOwnerId", pxUpdateOperator as "pxUpdateOperator", pxUpdateOpName as "pxUpdateOpName", pxExpireDateTime as "pxExpireDateTime", pxUpdateDateTime as "pxUpdateDateTime", pxLockHandle as "pxLockHandle", pxCreateDateTime as "pxCreateDateTime", pxUserHost as "pxUserHost" from PEGA_DATA.pr_sys_locks where pzInsKey = ? SQL Inserts: at com.pega.pegarules.data.internal.access.DBLockProviderImpl.releaseLock(DBLockProviderImpl.java:852) at com.pega.pegarules.data.internal.access.LockManagerImpl.releaseKey(LockManagerImpl.java:1461) at com.pega.pegarules.data.internal.access.UpdateProcessor.releaseReleaseOnCommitLocks(UpdateProcessor.java:830) at com.pega.pegarules.data.internal.access.UpdateProcessor.action(UpdateProcessor.java:262) at com.pega.pegarules.data.internal.access.UpdateProcessor.action(UpdateProcessor.java:82) at com.pega.pegarules.data.internal.store.DataStoreManager.doInTransaction(DataStoreManager.java:235) at com.pega.pegarules.data.internal.access.UpdateProcessor.processUpdates(UpdateProcessor.java:178) at com.pega.pegarules.data.internal.access.DatabaseImpl.commit(DatabaseImpl.java:2066) at com.pegarules.generated.activity.ra_action_pymobilesyncsavewitherrors_94f12e10ec1c399c79c1b90eb6174622.step2_circum0(ra_action_pymobilesyncsavewitherrors_94f12e10ec1c399c79c1b90eb6174622.java:240) at com.pegarules.generated.activity.ra_action_pymobilesyncsavewitherrors_94f12e10ec1c399c79c1b90eb6174622.perform(ra_action_pymobilesyncsavewitherrors_94f12e10ec1c399c79c1b90eb6174622.java:87) at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3553) at com.pegarules.generated.activity.ra_action_pzstoreandforwardprocessitems_e3ace12521e8fee4a7eb10b0c2ec6152.step4_circum0(ra_action_pzstoreandforwardprocessitems_e3ace12521e8fee4a7eb10b0c2ec6152.java:1221) at com.pegarules.generated.activity.ra_action_pzstoreandforwardprocessitems_e3ace12521e8fee4a7eb10b0c2ec6152.perform(ra_action_pzstoreandforwardprocessitems_e3ace12521e8fee4a7eb10b0c2ec6152.java:127) at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3553) at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10711) at com.pegarules.generated.activity.ra_action_pzstartsynchronization_e7f50ab567d3e43a65896bf9c9e9a74f.step6_circum0(ra_action_pzstartsynchronization_e7f50ab567d3e43a65896bf9c9e9a74f.java:505) at com.pegarules.generated.activity.ra_action_pzstartsynchronization_e7f50ab567d3e43a65896bf9c9e9a74f.perform(ra_action_pzstartsynchronization_e7f50ab567d3e43a65896bf9c9e9a74f.java:174) at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3553) at com.pegarules.generated.activity.ra_action_pzpackagingexceptioncatcher_99126f674af035c1d9054ee7f27c89f8.step1_circum0(ra_action_pzpackagingexceptioncatcher_99126f674af035c1d9054ee7f27c89f8.java:254) at

Steps to Reproduce

1. Submit applications while in offline mode.
2. Sync to server when you are online.

Root Cause

A defect in Pegasystems’ code or rules

The action "Go to previous task" is not releasing the lock on the work object in the case of optimistic locking.

Resolution

Apply HFix-49117.