topic Re: tSendMail Status in Talend Studio

tSendMail Status

DBLONDEL1643728674 — Sun, 29 Nov 2020 11:50:34 GMT

Hello,

I have an issue with tSendMail ... first, it works (in PRODUCTION) 99,99%, but sometimes I have issues, it never stops.

it is a classical tSendMail with Microsoft account and 1 file attached. the entire job usually last 2 minutes.

But, sometimes, it never stops ... blocking the next schedulling of the process.

You can see in the execution logs that the the tSendMail starts ... but never ended.

1.Do you know how to get a status of this tSendMail after a few minutes ?

2.If not, do you know how to interrupt a job after 10 minutes execution, even if not ended ? (

I mean, with a talend component inside the job ... do you know if such component exist ?

)

thanks in advance for you answers.

Re: tSendMail Status

Anonymous — Mon, 30 Nov 2020 06:28:01 GMT

Hello,

Is there any connection timeout exception when tSendMail is executed for a second or third time?

Here is a 'Die on error' check box on tSendMail component which is used to catch an error during the job execution.

Best regards

Sabrina

Re: tSendMail Status

DBLONDEL1643728674 — Tue, 01 Dec 2020 18:06:15 GMT

Hello Sabrina,

thank you for taking some time to look at my problem. As you can see, there is only one tentative to connect to smtp ... and it is successfull ... then, it never goes out the component ...

regards

Damien

Re: tSendMail Status

Anonymous — Wed, 02 Dec 2020 06:01:27 GMT

Hello,

If you want to stop your job when Execution Time is too long, please try this way.

Use a tPreJob to link to a tJava component. Calculate the current time and set it to the globalMap
In your tMap, create a tMap boolean variable (between the input and output tables) and use your start time globalMap value and compare to the current time (use the TalendDate routine). If the time difference is within 10 secs, set to True, else set to False.
Create another tMap output for when the time has expired. Use the tMap output filtering to decide which output to use based on the tMap variable result. For the output when you have run out of time, add any columns you may wish to report have not been done in time and connect that output to whatever component will fulfill your logging. Then connect that component to a tDie using a RunIf condition with some logic to identify that you do indeed want to kill the process (this is required because outputs from tMap components are always triggered even if there is no data).

Here is online component reference TalendHelpCenter: tDie

Best regards

Sabrina

Re: tSendMail Status

DBLONDEL1643728674 — Thu, 03 Dec 2020 16:51:46 GMT

Thank you for your efforts. I understand what you write but as you can see on the screen copy and associated message in the run logs, I have a display from tWarn before tSendMail, then I have a message 'connection so smtp has succeeded' ... and then, nothing. BUT as you can see, just after the tsendMail, I have another tWarn component ...

So, I am "entering" into the tSendMail ... but never go out ...

no tmap ... the tsendMail may have issues but is not allowing any interaction ...

regards

Damien

Re: tSendMail Status

Anonymous — Fri, 04 Dec 2020 03:01:15 GMT

@Damien BLONDEL, I am using Microsoft account to send email in my job every day, I don't have the problem so far, here is my settings, can you check if you have something different?

tsendmail is a component that works independently, can you try to change your job tSendEmail--main--tWarn to tSendEmail--OncomponentOK--tWarn? It will make the job more readable.

Where is the job executed? Talend Studio or TMC/TAC or third-party scheduler?

Regards

Shong

Re: tSendMail Status

DBLONDEL1643728674 — Fri, 04 Dec 2020 10:51:34 GMT

Bonjour Shong,

thank you for your answer. I have exactly the same settings on the tSendMail. I have splitted the mail into 5 as I am sending 5 files attached (size under the limit of my company's microsoft subscription limit) and will evaluate the impact in the coming hours.

I am using Talend Cloud Studio but job is executed on our own Windows Server (with a remote engine).

regards

Damien