Support Article
Frequent exceptions from an agent ProcessBatchJob
SA-76329
Summary
ProcessBatchJob agent generates PRRuntimeException in the logs.
Error Messages
Agent Pega-DecisionEngine #0: Data-Decision-StrategyExecution-BatchAgent.pzInitializeProcessEngine encountered an execution error. Restarting after delay.
com.pega.pegarules.pub.PRRuntimeException: unable to execute agent: Pega-DecisionEngine #0: Data-Decision-StrategyExecution-BatchAgent.pzInitializeProcessEngineUnable to open an instance using the given inputs: pxObjClass = "Data-System-Topology", pyName = "DEFAULT" at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:712) ~[prprivate.jar:?] at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:1139) ~[prprivate.jar:?] at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1366) ~[prprivate.jar:?] at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1109) ~[prprivate.jar:?] at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:990) ~[prprivate.jar:?] at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:805) ~[prprivate.jar:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_171] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_171] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
Steps to Reproduce
Unknown
Root Cause
A defect or configuration issue in the operating environment. The Pega Decision Strategy Manager (DSM) 'ProcessBatchJob' agent is responsible to execute batch simulations. In the out-of-the-box Pega Platform 8.1.2, the agent is disabled in the Agent Schedule. However, in the user's system, this agent is enabled from the Agent Schedule. Since, there are no node instances from the node topology (Decisioning > Configuration > Topology), the activity under the agent failed to obtain the node details because they are not present in the 'Topology'.
Resolution
Here’s the explanation for the reported behavior:
The ProcessBatchJob is disabled from the Agent schedule.
Create a new ProcessBatchJob in the application ruleset (if necessary) as part of the new Pega Marketing application implementation.
Published November 29, 2019 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.