Question

1
Replies
73
Views
JakubJasinski Member since 2016 2 posts
GE Healthcare
Posted: 8 months ago
Last activity: 8 months ago

How to extract what's behind a generic "RDB-Save failed" error at activity/agent runtime

Hello community!

Recently I've been working on an enhancement solution for some of agents (we're in 8.2.2 version and I know that we should replace them with job schedulers - we're not there yet but want to do it in the future) that we're using for getting the data from external sources using REST services in order to be in sync.

Long story short, agent execution starts with triggering a db procedure using RDB-Save method. We were observing that the agent fails occasionally in this step and decided to add some exception handling to see what the error message is as well as clearing the activity status and page messages so that the execution is not failing/crashing agents. 

We're jumping to a logging mechanism after a step status fails, logging the fact that we failed as well as using a function getWorstMessage to see what the exception is, storing it in the parameter and then posting this into the external database table (we prefer db than checking logs through pega or kibana). 

Two weird things that are happening: 

1. Even though we're clearing the activity status and page messages the agent crashes after RDB-Save method fails.

2. When we capture the error message using getWorstMessage function we're only seeing "RDB-Save failed" error with no details.

Questions: 

How to make sure that RDB-Save method failure won't stop agents while running?

How to extract more details regarding the error behind RDB-List failed? 

 

Activity Captured

Reporting Healthcare and Life Sciences Senior System Architect
Share this page LinkedIn