topic Re: Node (trun job) is in a recursive loop in Talend Studio

Node (trun job) is in a recursive loop

EV89 — Fri, 19 Mar 2021 18:03:11 GMT

Hello,

i see a talend alert on my trun job component. The alert message says Node (trunjob1) is in a recursive loop (see screenshoot). Whate are the implications of this alert? why this alert appear?

i think the reason is a subjob that contais a tloop node. But the tloop is not an infiinite loop so i don't understand the alert. After maximum three execution loop exit and the job continues.

Can anyone explain to me? i am afraid of possible errors.

N.b if run condition to exit from while loop

((Integer)globalMap.get("tDBOutput_1_NB_LINE_INSERTED")) > 0 || ((Integer)globalMap.get("tLoop_1_CURRENT_ITERATION")) == 3

thanks

Re: Node (trun job) is in a recursive loop

Anonymous — Mon, 22 Mar 2021 04:50:26 GMT

Hello,

On which talend build version you got that? Is there any infinite loop in your work flow? Could you please post the whole job design screenshots here?

Best regards

Sabrina

Re: Node (trun job) is in a recursive loop

Anonymous — Mon, 22 Mar 2021 05:28:31 GMT

What is the Then option on tWaitForFile? If you want tRunJob to run, the option should be 'Exit loop' to exit the loop and then trigger other subjobs.

Regards

Shong

Re: Node (trun job) is in a recursive loop

EV89 — Wed, 24 Mar 2021 08:25:40 GMT

Thanks for your hint,

yes i have set up the twait file for exit loop and prosegue with the flow execution (see screenshot)

Re: Node (trun job) is in a recursive loop

EV89 — Wed, 24 Mar 2021 08:35:26 GMT

Hi, thanks for your help. My talend is the version: 7.3.1.

The flow is composed by almost entirely job with only tmysql input, tmap and tmysql output. Only one job contains a loop. I attach you the loop image on the discussion files ( As reply i can only attach one image) .

N.b if run condition to exit from while loop

((Integer)globalMap.get("tDBOutput_1_NB_LINE_INSERTED")) > 0 || ((Integer)globalMap.get("tLoop_1_CURRENT_ITERATION")) == 3

thanks

Re: Node (trun job) is in a recursive loop

PSanadi — Mon, 05 Jul 2021 08:00:55 GMT

I am also getting same warning on tRunJob in Talend 7.3, I have tParallel and tFlowtoIterate components. What is the impact for this?

Re: Node (trun job) is in a recursive loop

MarcelR — Wed, 06 Jul 2022 12:23:28 GMT

Hello,

we also getting the same warning on tRunJob in Talend 7.3. We dont have any loop components in our sub-jobs. But we use tFlowtoIterate. In all sub-job how we use an iterate we getting this warning. But I dont understand the warning.

What is the impact for this warning?

Regards

Marcel

Re: Node (trun job) is in a recursive loop

Anonymous — Thu, 07 Jul 2022 03:46:55 GMT

Hello,

Would you mind posting your current job design screenshots here which will be helpful for us to address your issue.

Best regards

Sabrina

Re: Node (trun job) is in a recursive loop

MarcelR — Thu, 07 Jul 2022 14:12:23 GMT

Hello,

thx for you fast feedback.

i hope, i can give an overview. 🙂 OK Lets go.

First, the main Job: with warning on Send_Mail.

Send-Mail-sub-Job:

InitJob

When I deactivate InitJob, for sub-job Send_Mail

No warning on Send_Mail, in the main Job.

Best regards

Marcel

Re: Node (trun job) is in a recursive loop

anselmopeixoto — Fri, 16 Jun 2023 13:07:51 GMT

I just went through the same problem and it was being caused by a child Job being called at different levels of a Job hierarchy.

@Not defined Not defined I hope you managed to get rid of this warning already, but if not, I believe it was being cause by the "InitJob" and "LogPublisher" Jobs being called at different levels of the hierarchy.

Re: Node (trun job) is in a recursive loop

MarcelR — Tue, 20 Jun 2023 06:33:19 GMT

@Anselmo Peixoto Thank you for this hint. No, the warning is still there, the difference from before, we just ignore it. 😉

What goes against this theory, why is it enough if only "InitJob" is disabled. "LogPublisher" is still active on both levels.

Re: Node (trun job) is in a recursive loop

anselmopeixoto — Wed, 21 Jun 2023 14:26:47 GMT

Hi @Not defined Not defined

Thanks for sharing it. That's odd, but I believe the reason is that "LogPublisher" is connected to a tLogCacher whereas "InitJob" is connected to tPrejob.

My idea is that since tPrejob guarantees that what's connected to it will always run, perhaps it causes the "recursive loop" interpretation by Studio, while tLogCatcher's behavior is "conditional" and therefore Studio interprets it as a loop breaker.