Subjob doesn't start when deployed

[Anonymous]

Hello all, 

This problem is related to the former one I posted, where the whole job didn't run after deployment. This was solved (https://community.talend.com/t5/Deployment/Built-job-doesn-t-run-when-deployed-on-Windows-Server-201...)

However, it seems that only the mainjob is running, it stops every time at the point where it would start a Subjob. 

And the strange thing is.. it stops without throwing an error or anything.. so I have nothing to go on.. 

And still it applies that on my computer in Talend it works fine, but when deployed on another server (and running under another account) it doesn't start the subjob. 

Any ideas what could be the problem? 

[Anonymous]

Does it actually stop, or just not continue for a long time? What do your logs show? You will need to give us a lot more information so that we can understand exactly what is happening.

[Anonymous]

Hi, 

It stops. And it says it just ran succesfully in the Task scheduler, so no errors there.. 

I have built in logging that goes to a database, so I can follow the flow, and the logging continues till the component just before the tRunJob. I indicated it in the screenshot of my mainjob with colours. So the circled  component is the last logged component.. and the arrows indicate where the job is stopped..  In the subjobs themselves I also have logging, so if it would stop somewhere halfway there, I would also see it, but it doesn't even reach the first component. 

If there is an error, it should have given an error in the logging as well, so that's also weird that that doesn't happen. 

So, it picks up the file in tFileList, moves it to another directory (which i can follow as well), directs to a certain flow, but then at the tRunJob it just stops... 

InkedIDandScanning_Mainjob_SF2CORE_0.1_LI.jpg

[Anonymous]

OK, I see what you are doing. It's a big job. It might make it a bit easier to understand if you break down the job into more child jobs, but that is up to you 🙂

Can you show me the configuration of the tRunJobs?

[Anonymous]

Hi, 

Well, as soon as I get the child jobs working.. I might consider that It indeed grew way bigger during the process than on beforehand estimated..

Anyway, added a screenshot of the configuration, is that what you meant? 

Nothing else in the advanced settings, except for Catch tstatistics. 

configuration_tRunJob.PNG

[Anonymous]

OK, that looks pretty standard. I notice most of the tRunJobs that fail to run are connected to RunIfs. I know this is a pain, but can you replace the tRunJobs with tJava components with System.out.println() calls in them. When you run the job these should be fired. If they are not, then it could be your RunIfs are not firing as you expect.

[Anonymous]

Hi, 

I tried as you suggested, but the tJava did run, so the if-statement seems not to be the problem.. 

What could be the issue with running a subjob, that if you run it from a different account/server, it suddenly doesn't work? 

[Anonymous]

I have seen an issue with the Dynamic option switched on, which is why I was curious to see your tRunJob config. But it is not that. The fact that the job doesn't error indicates that it is probably not a memory issue. It *could* be that your child jobs are not built into your parent job. To see that you would have to open the Jar (use 7Zip) and that would be a Talend bug.

One other thought, are you running in the JobServer or the Runtime (Apache Karaf)?

[Anonymous]

Hi, 

Well, but when deployed on my own pc, same artifact, it runs perfectly, so for sure not being built in is not the issue. 

I am running them from the Windows Task scheduler. They are batchwise jobs (.bat). 

[Anonymous]

So this isn't in the Enterprise Edition? Sorry, I thought it was running on a Talend server.

Are you comparing running in the Studio against running as a compiled Jar file (from a .bat file). Or are you running the exact same Jar file, just on different machines? If so, are your Java environments the same? You should be using the JRE included with the JDK install as well. There are subtle differences between the JRE on its own and the JRE included with the JDK.