Node (trun job) is in a recursive loop

[EV89]

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

[Anonymous]

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

[Anonymous]

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

[EV89]

Thanks for your hint,

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

[EV89]

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

[PSanadi]

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

[MarcelR]

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

[Anonymous]

Hello,

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

Best regards

Sabrina

[MarcelR]

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

[anselmopeixoto]

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.