topic Re: Ignore connection error to avoid exit code = 1 in Talend Studio

Ignore connection error to avoid exit code = 1

Anonymous — Thu, 27 Sep 2018 20:57:11 GMT

Hi everyone,

I have a job that connects to 15 servers and almost everyday one of them gives a connection error, it's normal, sometimes the equipament is not avaialable, but the problem is I have a schedule inside Control-M to execute this talend job automatically and everytime the job on talend finishes with exit code = 1, control-M flags and opens an incident through our ITSM tool. Our team would like to avoid this incident since this communication error is a normal behaviour for this job. Does anyone knows how can I skip this error to job finished with exit code = 0?

This is the scenario:

I try to connect in one server, if there is a connection failure, talend goes to t_die, store in tlogcatchcer and continue the execution trying to connect in another server.

But the moment this communication failure happens, it is stored in execution log after the job runs entirely, the exit code is = 1. Is there a way to keep saving this communication failure in tlogcatcher but ignoring this kind of error during job execution to finish with exit code = 0?

This is the error configured on tdie component: even priority configured as "information",

the exit code is 1.

Re: Ignore connection error to avoid exit code = 1

Anonymous — Sat, 29 Sep 2018 09:29:14 GMT

Hello,

Please make sure that you Execute the right application for your system.

32 bit studio is for 32-bit systems and that's the same for 64 bit application.

This issue is probably caused by insufficient memory. Have you tried to allocate more memory to your studio by modifying .ini file to see if it works?

Best regards

Sabrina

Re: Ignore connection error to avoid exit code = 1

Anonymous — Wed, 03 Oct 2018 12:53:46 GMT

Hello, Thank you for your reply.

I'm using the correct version and the job is executed corretly, the issue is regarding the exit code because on this job scenario there will always be a communication link failure in one if the tDBInput (my SQL). What I would like to do is that Talend ignores this communication link failure (that is normal in this case) and end the job as exit code = 0 to avoid an alarm in our monitoring application. It should only set exit code = 1 if the error is different from "Erro de conexão172.16.25.2Communications link failure" which is the die message I configured in tdie component.

Please, do you know a way to personalize that?

Picture attached

Thanks in advance.

Snap 2018-10-03 at 08.52.44.jpg
Snap 2018-10-03 at 08.53.21.jpg