Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
When I run my job from the command-line (using the shell script), is there any way to make it show a stack trace of the error? All I get is:
Exception in component tSystem_1
Exception in component tSystem_1
Yes unfortunately the tParallel component is not part of the open source release. In this case you can only check the job output at its end.
Or you export the job as a standalone job and sends the outputs to a file (as Sabrina already suggested) and another job running parallel (checks the output file and sends the stack trace).
Why do you need the stack trace in a email? I would design the job and the tDie's in a way to have more meaningful messages. From my point of view this is a be far better approach than reading stacktraces to find the problem.
As far as the stack trace on email its because the job is supposed to be running everyday on an external server, so if anything goes wrong, i wanted to have all the possible information about what happened.
At least this was the ideia
1. Use the tAssertCather component to get the exception object.
2. Create a Routine class to handle the exception to a string
public static String getStacktrace(Object o)
{
StringWriter sw = new StringWriter();
PrintWriter pw = new PrintWriter(sw);
((Throwable) o).printStackTrace(pw);
return sw.toString(); // stack trace as a string
}
2. Create a Routine class to handle the exception to a string
public static String getStacktrace(Object o)
{
StringWriter sw = new StringWriter();
PrintWriter pw = new PrintWriter(sw);
((Throwable) o).printStackTrace(pw);
return sw.toString(); // stack trace as a string
}