Question
Bits In Glass
GB
Last activity: 8 Dec 2016 2:35 EST
Regarding agent alert triggered.
Hi, in my project i have encountered the "PEGA0010".
I understand that there was an error while processing which generated this error.
Can you guide me how to look into this?
Agent [SPRPM] activity [RTG-Work.PCRWorkBasketAgentActivity] queue number [6] disabled due to execution errors ErrorMsg: com/pega/pegarules/priv/util/StackTrace
so Agent Name : SPRPM
In agent in class : RTG-Work
Activity : PCRWorkBasketAgentActivity
is the queue number here referes to the step 6 of activity?
and what does com/pega/pegarules/priv/util/StackTrace mean?
***Updated by moderator: Lochan to update Categories***
Accepted Solution
Pegasystems Inc.
US
Advanced Agents disable themselves if an Exception occurs that is not handled.
A stack trace will be generated. Look at SMA -> Agents.
My guess is that your Advanced Agent either completely lacks error checking or is not checking for errors at the step where the error is occurring.
Advanced Agent Activites should be written like Java methods, i.e., try + catch + finally.
Check for errors in Advanced Agent Activities liberally. When an error is detected jump to a "catch" step that executes Log-Message + stack trace. For the message itself output context information followed by the function: getWorstMessage(tools).
Usually a stack trace indicates on what step an Exception is thrown. Isn't the Exception's stack trace visible in the logs?
Incessant Technologies
IN
Hi,
The alert identifies the agent name, agent activity, queue number (index of this agent queue from Rule-Agent-Queue instance), and the event that triggered the alert.
For more detail please see - https://docs-previous.pega.com/system-administration/84/pega0010-alert-agent-processing-disabled
Accepted Solution
Pegasystems Inc.
US
Advanced Agents disable themselves if an Exception occurs that is not handled.
A stack trace will be generated. Look at SMA -> Agents.
My guess is that your Advanced Agent either completely lacks error checking or is not checking for errors at the step where the error is occurring.
Advanced Agent Activites should be written like Java methods, i.e., try + catch + finally.
Check for errors in Advanced Agent Activities liberally. When an error is detected jump to a "catch" step that executes Log-Message + stack trace. For the message itself output context information followed by the function: getWorstMessage(tools).
Usually a stack trace indicates on what step an Exception is thrown. Isn't the Exception's stack trace visible in the logs?