what is the harm/impact of singleton exception in Log file for Activity-End
Hi,
we are getting below exception while using Activity-End in Pega 7.1.6. Is there any harm or impact on system because of this exception?
com.pega.pegarules.pub.runtime.ActivityTerminateException: This is a singleton exception object and the stack trace below does NOT reflect the actual point of failure. To see the actual trace, set Initialization/UniqueActivityTerminateExceptions = true at com.pega.pegarules.session.internal.mgmt.Executable.<clinit>(Executable.java:441) at com.pega.pegarules.session.internal.PRSessionProviderImpl.getExecutableInstance(PRSessionProviderImpl.java:1744) at com.pega.pegarules.generation.internal.cache.appcentric.RACacheAppCentricImpl.reloadCache(RACacheAppCentricImpl.java:1762) at .................
Thanks,
Kartheek
PEG
US
See SA-34920. The Activity-End throws an exception, and activities are not intended to throw exceptions. The error you are seeing is a mild complaint about that. As you don't want your application to depend upon invalid operations, see if you can find some other way to abort things.
Virtusa
US
Hi Coher,
we have a standard agent which performs some business logic. During this process our application will fetch data from 4 external systems through services.
If any service is down then the queue item is going to Broken-Queue status.
Our New Requirement is to Re-Queue the task again for 3 attempts upon service failure . We are doing Queue-For-Agent after service failure followed by "Activity-End" so that it will not go to steps.
Question: Will this Singleton exception has any impact/side effect on application?
Thanks,
Kartheek
Pegasystems Inc.
US
Kartheek,
Instead of doing an activity-end, could you make the last step in the activity be an error step and then jump to there? The exception itself shouldn't have any major impact, but it will clutter your logs. If you want to log the failure, you could add a log statement on your error step. That would make it more meaningful.
Thanks,
Mike
Pegasystems
US
Activity-end is rather heavy-handed, as it aborts all levels of activities, and if you are at all unsure about the activities that called yours, it is safer to use exit-activity instead, and design your calling activity detect via the status (see StepStatusFail and related documentation) that your called activity encountered an issue.
Virtusa
US
Hi ,
we are catching the exception and logging with InforForced along with Activty-End.
we have lot of inner activities, Activity A-->B-->C-->D-->E-->F etc, if we have to exit each activity based on a flag will be a tedicious task, so we went with Activity-End.
Service fail in production will happen very rarely,but i want to make sure that "Activity-End" will not cause any other issues.
Thanks,
Kartheek