topic Re: [resolved] OnSubjobOk is not working as expected in Talend Studio

[resolved] OnSubjobOk is not working as expected

_AnonymousUser — Mon, 26 May 2014 08:02:13 GMT

Hi All,
I have multiple subjobs with the components tFixedFlowInput, tFlowtoIterate & tRunJob.
When I use OnSubJobOk on tFixedFlowInput to another tFixedFlowInput of another subjob, it is not working as expected. The other jobs are running fine though the subjob is throwing an error.
FYI, I have selected "Die on child error" option in tRunJobOk component.

Thanks,
Siva

Re: [resolved] OnSubjobOk is not working as expected

Anonymous — Mon, 26 May 2014 08:46:11 GMT

Hi,
Would you mind uploading your current job design screenshots into forum so that we can see if your workflow is correct in logic.
Best regards
Sabrina

Re: [resolved] OnSubjobOk is not working as expected

Anonymous — Mon, 26 May 2014 09:30:50 GMT

Hi Sabrina,
PFA the screenshot of talend job.

Thanks,
Siva

Re: [resolved] OnSubjobOk is not working as expected

Anonymous — Mon, 26 May 2014 09:51:39 GMT

Hi Siva
What's the error message you get on the console?
Shong

Re: [resolved] OnSubjobOk is not working as expected

Anonymous — Mon, 26 May 2014 10:23:00 GMT

Hi Shong,
In the subjob, I have one context.variable as status variable and I'm the providing the values as SUCCESS/FAILED. If, it contains value as FAILED then I have used tDie Component to stop the complete job.
Error message is something like "Child job has failed" as it has status as FAILED.
Here my concern is, If the subjob has failed with any kind of issue, then the other subjob having OnSubjobOk won't run right. Correct me If I'm wrong with it.

Thanks,
Siva

Re: [resolved] OnSubjobOk is not working as expected

Anonymous — Mon, 26 May 2014 10:32:56 GMT

Hi
It depends on the 'die on error' option on tRunJob even though the child job has an error:
if 'die on error' option is checked, the exception will be thrown out to the main job, the main job will die and stop to run, the subjob linked with onsubjobok will not be fired.
if 'die on error' option is not checked, the exception will be captured and handled by program, the main job will continue to run, the subjob linked with onsubjobok will be fired.
Shong

Re: [resolved] OnSubjobOk is not working as expected

Anonymous — Mon, 26 May 2014 10:38:40 GMT

Hi Shong,
FYI, I have selected the "Die on child error" on tRunJob component. But Still the subjob having onSubjobOk is running.

Thanks,
Siva

Re: [resolved] OnSubjobOk is not working as expected

Anonymous — Tue, 27 May 2014 14:21:20 GMT

Hi Shong,
FYI, I have selected the "Die on child error" on tRunJob component. But Still the subjob having onSubjobOk is running.

Thanks,
Siva

If the subjob linked with onsubjobok is still running, means there is no error/exception occurs in the child job. If the child job really has an error/exception, and the 'die on child error' box is checked, you will see an error message as read below on the console when running the main job.

the end is near
Exception in component tRunJob_1
java.lang.RuntimeException: Child job running failed
	at

Shong

Re: [resolved] OnSubjobOk is not working as expected

Anonymous — Wed, 28 May 2014 17:42:41 GMT

Hi Shong,
I have got the following exception:
Exception in component tRunJob_2
java.lang.RuntimeException: Child job running failed
at ......
But Still the remaining process is continued.
PFA the screenshot of the talend job.
Thanks,
Siva

Re: [resolved] OnSubjobOk is not working as expected

Anonymous — Thu, 29 May 2014 02:46:44 GMT

Hi Siva
Which version are you using? I have tried to reproduce this problem in v5.4.1, but it can't be reproduced, it works as expected. If you are using an older version, try to download the newest version and test it again.

Shong

Re: [resolved] OnSubjobOk is not working as expected

Anonymous — Thu, 29 May 2014 06:52:29 GMT

Hi Shong,
Thanks for your time.
I'm using the v5.3.1.
Is there any way to work it in the above mentioned version. It would be really helpful to me if you provide the way to work it in the v5.3.1.

Regards,
Siva

Re: [resolved] OnSubjobOk is not working as expected

Anonymous — Thu, 29 May 2014 10:22:38 GMT

Hi Siva
I have tested this problem in the v5.3.1 and I got the same problem, it was a bug which only occurs when 'Enable parallel execution' box is checked on iterate link, it works normal if this box is not checked. So, you can resolve this issue with one of the following ways:
- Disable parallel execution on the iterate link.
- Upgrade to the new release if you are using community version, or open a ticket in our support portal to request a patch if you are using Talend enterprise product.
Shong

Re: [resolved] OnSubjobOk is not working as expected

Anonymous — Thu, 29 May 2014 11:56:16 GMT

Hi Shong,
Thanks for your response.
I can't disable the parallel execution on the iterate link as it is one of the most important part in my business process.
I have tried few things to get the same behavior of OnSubjobOk. But those are working in some scenarios & failed in some other scenarios.
Is there any possibility to have a Skype Call/ Web Call with you ? It would be really helpful to me.

Thanks
Siva

Re: [resolved] OnSubjobOk is not working as expected

Anonymous — Thu, 05 Jun 2014 05:06:06 GMT

Hi Siva
If you don't plan to upgrade your studio to a new release, you have to redesign the job to avoid this issue, the workaround can be:
- Define a flag in the child job to indicate the job runs fine or failure.
- Read this flag in the main job, and use runIf connector instead of onsubjobok, to fire other processing based on the condition.
Refer to this KB article:
Can I define a variable that is accessible from multiple Jobs?
Shong

Re: [resolved] OnSubjobOk is not working as expected

Anonymous — Thu, 05 Jun 2014 07:12:16 GMT

Hi Shong,
Thanks for your response.
I already implemented the same flag kind of idea by creating one global variable. It's working fine.

Regards,
Siva

Re: [resolved] OnSubjobOk is not working as expected

Anonymous — Thu, 05 Jun 2014 09:07:56 GMT

Hi Shong,
Thanks for your response.
I already implemented the same flag kind of idea by creating one global variable. It's working fine.
Regards,
Siva

Great! Thanks for your feedback, this topic can be marked as resolved now.
Shong