Support Article
AgentBulkProcessing agent is failing with lock exception
SA-7926
Summary
The AgentBulkProcessing agent is failing when attempting to lock Assign-Schedule-Future instances.
Error Messages
2015-03-24 07:38:41,252 [ PegaRULES-Batch-1] [ STANDARD] [ MyApp:01.05.01] (ernal.async.BatchRequestorTask) ERROR - Batch activity "Assign-.AgentBulkProcessing" threw:
com.pega.pegarules.pub.PRRuntimeError: Save, Delete or Commit has failed because lock "ASSIGN-SCHEDULE-FUTURE 20150324T113748.032 GMT!462DDF5280308B2022F6B959D736B4A1" is not held
at com.pegarules.generated.updateBPQueue_060201_XOyp7ivZI959dom8FAM$WQ.updateBPQueue06_02_01(updateBPQueue_060201_XOyp7ivZI959dom8FAM$WQ.java:267)
at com.pegarules.generated.updateBPQueue_060201_XOyp7ivZI959dom8FAM$WQ.invoke(updateBPQueue_060201_XOyp7ivZI959dom8FAM$WQ.java:81)
at com.pega.pegarules.generation.internal.library.LibraryRuntime.resolveAndinvokeFunctionViaReflection(LibraryRuntime.java:131)
at com.pega.pegarules.generation.internal.library.LibraryRuntime.invokeLibraryRuntime(LibraryRuntime.java:108)
Exception at 20150324T171459.076 GMT: com.pega.pegarules.pub.database.LockGoneException: Save, Delete or Commit has failed because lock "ASSIGN-SCHEDULE-FUTURE 20150324T171332.878 GMT!462DDF5280308B2022F6B959D736B4A1" is not held From: (B499DE6BE61CD8380A0C8C924B4EB61B4) at com.pega.pegarules.data.internal.access.Deleter.deleteDeferred(Deleter.java:344) at com.pega.pegarules.data.internal.access.DatabaseImpl.deleteDeferred(DatabaseImpl.java:5280) at com.pegarules.generated.updateBPQueue_060201_XOyp7ivZI959dom8FAM$WQ.updateBPQueue06_02_01(updateBPQueue_060201_XOyp7ivZI959dom8FAM$WQ.java:257) at com.pegarules.generated.updateBPQueue_060201_XOyp7ivZI959dom8FAM$WQ.invoke(updateBPQueue_060201_XOyp7ivZI959dom8FAM$WQ.java:81) at
Steps to Reproduce
Run the AgentBulkProcessing agent.
Root Cause
The root cause of this problem is misconfiguration in the PRPC operating environment. AgentBulkProcessing is designed to detect and work around locked work objects. Attempting to enable the agent on more than one node may cause contention for locks.
Resolution
Perform the following local change:
Only run the Assign-.AgentBulkProcessing on one node of a multinode cluster.
See this Help topic:
https://pdn.pega.com/sites/default/files/help_v62/procomhelpmain.htm#concepts/concepts2/understandingpegaprocomomagent.htm?Highlight=bulk processing agent
Published May 4, 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.