Question
Capgemini India Private LTD
IN
Last activity: 8 Sep 2017 7:07 EDT
Want to get exception detail in a property
If any step in an activity throws exception then we should catch the whole java stack trace in a property and have to send this stack trace by email.
Steps to Reproduce
I used the below statement in a property-set method and applied exception handling to catch the exception
Local.mydata = 1/0
I can only catch pxThread.pxMethodStatus in a string to display. But I have to catch the whole java stack trace so that I can send email to Product Support team with fill stack trace of the exception.
pxThread.pxMethodStatus can only show the below statement.
Fail: Java Exception: java.lang.ArithmeticException: / by zero
If we dont apply anything in JUMP button for exception handling then we see Exception event in tracer. if we click on Exception event in tracer then we see the full stack of java exception that is what we needed somehow.
Message was edited by: Lochan to add Category
Pegasystems Inc.
US
Hi Prashant,
Would one of the getStackTrace functions be helpful here? I see one in the Pega-Rules Utilities library and another one in the Pega-ProCom ProcessEngineStatus library.
Carissa
Pegasystems
US
Define stackTrace as a local var in your activity params tab and then put this in a java step:
Throwable t = new Throwable();
java.io.StringWriter sw = new java.io.StringWriter();
java.io.PrintWriter pw = new java.io.PrintWriter(sw);
t.printStackTrace(pw);
pw.close();
pw.flush();
stackTrace = sw.toString();
IT
SK
Hello, colleagues, this is a valid issue. We have faced the same problem. Building stacktrace in a java step is not a good solution, because this would be a different stacktrace from the one which was created when the failure occured. It is a pitty that Pega does not allow to hold it as it is often the only way to diagnose the problem.
In case if we are in context of flow a parameter ProblemFlowStackTrace is populated in case if DSS Pega-Engine • prconfig/initialization/displayexceptiontraceback/default is set to true:
However, the problem accurs when we are outside of the flow - it seems that nothing does a back up of a stacktrace during the failure and therefore it is impossible to get the diagnostic information anywhere but only in the logfile.
Updated: 8 Sep 2017 6:12 EDT
WFC
IN
Hi IVANG,
Completely agree with you and got the context. Facing the same issue. Is there any way we can get at least failed activity name/ step details if not the complete stacktrace !
IT
SK
@Rathnach, thanks for your feeback. This issue is causing trouble for our team and we were thinking about raising an SR, but did not have enough time for it yet. If this issue causes trouble for you also - maybe you could raise an SR and let us know here how it goes. We would do the same when we have time to breath.
Pegasystems Inc.
IN
Do let us know the SR number once you create it. We wil tag that to the original post above and track it till resolution.
Regards,