topic Getting full Exception object. in Talend Studio

Getting full Exception object.

Anonymous — Sat, 16 Nov 2024 10:19:35 GMT

Below is my job. I am trying to get the Exception object using tAssertCatcher, but I am not able to do so.
My tFileOutputDelimited throwing the following error :

Exception in component tFileOutputDelimited_1
java.io.FileNotFoundException: C:\out.csv (Access is denied)
at java.io.FileOutputStream.open0(Native Method)
at java.io.FileOutputStream.open(Unknown Source)
at java.io.FileOutputStream.<init>(Unknown Source)
at java.io.FileOutputStream.<init>(Unknown Source)
at first_project.temp_0_1.temp.tRowGenerator_1Process(temp.java:597)
at first_project.temp_0_1.temp.runJobInTOS(temp.java:1720)
at first_project.temp_0_1.temp.main(temp.java:1573)

I want to get the exception object and take necessary action, but I am getting all the values empty in tAssertCatcher.

The following is my tLogRow :

first_project.temp_0_1.temp.main(temp.java:1573)
.------+---+-------+---+--------+------+------+---------+-----------+---------.
| tLogRow_1 |
|=-----+---+-------+---+--------+------+------+---------+-----------+--------
|moment|pid|project|job|language|origin|status|substatus|description|exception|
|=-----+---+-------+---+--------+------+------+---------+-----------+--------
'------+---+-------+---+--------+------+------+---------+-----------+---------'

My question is : How can I get the exact Exception object for any component when any exception occurs, so that I can take necessary action based on the exception, also I want to start the job after the action is taken against the exception.

Thanks.

Re: Getting full Exception object.

Anonymous — Wed, 12 Oct 2016 10:25:02 GMT

Hi,
The tAssert component works alongside tAssertCatcher to evaluate the status of a Job execution.
Could you please take a look at the related scenario in component reference:TalendHelpCenter:tAssert to re-design your workflow?
Best regards
Sabrina

Re: Getting full Exception object.

Anonymous — Tue, 18 Oct 2016 10:49:17 GMT

Hi Sabrina,

Now I have modified my Job and I am getting the exception object.

In the job below you can see that I have used onComponentOk which is completely wrong according to me.
Because the component tFileOutputDelimited_1 is not ok, it contains error, So I am not understanding why tAssertCatcher working correctly and giving me the exception object.

Where as in my original question the behavior was straight forward i.e:. If the tFileOutputDelimited contains error then go to tAssertCatcher and give me the exception object which did not worked as expected but the above job is working fine and giving me the exception object which is exactly what I need.

My question is : Is this correct ?
According to my understanding it is not.

If possible please give me explanation to this behavior, as I am not able to understand this.

I hope I am clear with my doubt and question.

Best Regards

Shivkumar

Re: Getting full Exception object.

Anonymous — Wed, 19 Oct 2016 08:47:01 GMT

Hi,
Have you already checked the related scenario in component reference:TalendHelpCenter:tAssert?
The tAssert component works alongside tAssertCatcher to evaluate the status of a Job execution.
The work flow should be:trowgenerator-->tfileoutputdelimited-->onsubjobok-->tAssert
tAssertCatcher -->tjavarow-->tlogrow
Best regards
Sabrina

Re: Getting full Exception object.

Anonymous — Wed, 19 Oct 2016 09:50:50 GMT

Hi,

Sorry to trouble you once again.

I again modified my job.This time I did not made any connection to tAssertCatcher and then I tried to run it.
I found the exception object. I experimented my job with error and with out error.
So according to me I have following conclusions.

1. The tAssertCatcher does not need any connection and it works at overall job level.
2. When an exception occurs it is triggered automatically and collects info about exception , which you can use , like the tStatCatcher which works at job level.

Below is my modified job.

My tAssertCatcher collects data and works only when exception occurs else not.

If you feel anything inappropriate or incorrect please correct me.

Thank you for your response and support.

Re: Getting full Exception object.

Anonymous — Wed, 19 Oct 2016 09:57:32 GMT

Hi,
You should use tAssert component in your work flow which is used to provide the Job status messages to tAssertCatcher.
In this way, tAssertcatcher can work at overall job level.
[font=Verdana, Helvetica, Arial, sans-serif]Note:T[/font]he tAssert component works alongside tAssertCatcher to evaluate the status of a Job execution.
Best regards
Sabrina