Question

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***

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Correct Answer
November 18, 2016 - 7:32am

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?

 

 

Comments

Keep up to date on this post and subscribe to comments

November 18, 2016 - 7:20am

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://pdn.pega.com/understanding-pega0010-alert-agent-processing-disabled

Pega
November 18, 2016 - 7:32am

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?

 

 

December 8, 2016 - 2:35am

I have seen that issue occured as the database got migrated to oracle 12c from oracle 11.