Question

11
Replies
1188
Views
jagadeeshm2569 Member since 2015 2 posts
cisco
Posted: September 24, 2018
Last activity: December 5, 2018
Closed

Agent Failure status not captured correctly in my activity for the class "Data-Agent-Queue"

Hi,

We have written an automation agent which will check if the agent is down in the current node. If its down, it will restart the agent. We are using "Data-Agent-Queue" class to get the list of all agents for the specific ruleset of that node. To get the details of each agent of that ruleset, we are using "Embed-Rule-FutureQueue" class. This way if .pyFatalMessage has an error, we are restarting the agent. However, for some cases we have observed that though in SMA there is fatal message for that agent, the property .pyFatalMessage in tracer/clipboard is null. For these cases, we are unable to validate agent status.

I checked for a particular application where there are 2 specific agents that are down. As part of my activity tracing, one of the agent has pyfatalmessage property with fatal message whereas the other agent has null value in pyfatalmessage even though in SMA it is has some error message.My analysis is that the one which has null value in pyfatalmessage has 60,000 characters in “exception Info” of SMA whereas the other one which has value in pyfatalmessage has around 8000 characters in "exception Info" of SMA.

Not sure if the length has to do with it.

***Edited by Moderator Marissa to update SR Details; update platform capabilities***

Pega Platform Data Integration SR Exists
Moderation Team has archived post
Share this page LinkedIn