catch runtime exceptions in Talend DI - tLogCatcher, tDie, "die on error"

Highlighted
Seven Stars

catch runtime exceptions in Talend DI - tLogCatcher, tDie, "die on error"

Hello everyone,

 

I am seeking clarification on error handling in Talend DI (version 6.4).

 

If I use tLogCatcher to catch all exceptions in my Talend DI job then it appears that I must also use "On Error" flow to a tDie component (or to tWarn).

If this correct? If there a way to make it catch all errors without explicit tDie/tWarn on-error flows ?

 

I have tLogCatcher -> tFileOutput (or tLogCatcher ->tMap -> tFileOutput) to catch all errors.

 

This did not work until I explicitly added tDie to my sub-job "on Error" flow. Now it works.

 

If I check the "die on error" for a given component - is this same as flow to tDie on error i.e. will the error be caught by tLogCatcher  or do I still need explicit on-error tDie ?

 

Not all components have a "die on error".

 

thanks

 

 

Eight Stars sgv
Eight Stars

Re: catch runtime exceptions in Talend DI - tLogCatcher, tDie, "die on error"

Hi ,

 

I'm just using tLogCatcher --- tFileOutputDelimited to log my error and it's work fine.

Personnaly I use tDie or tWarning if i want to take care about special case.

But if you have something like : Job father calling Child Job , you have to put your tLogCatcher --- tFileOutputDelimited in two jobs otherwise, child job's error is not catched.

 

SGV

 

 

 

What’s New for Talend Spring ’19

Watch the recorded webinar!

Watch Now

Best Practices for Using Context Variables with Talend – Part 4

Pick up some tips and tricks with Context Variables

Blog

How Media Organizations Achieved Success with Data Integration

Learn how media organizations have achieved success with Data Integration

Read

Definitive Guide to Data Integration

Practical steps to developing your data integration strategy.

Download