topic Re: Built job doesn't run when deployed on Windows Server 2012 in Talend Studio

Built job doesn't run when deployed on Windows Server 2012

Anonymous — Sat, 16 Nov 2024 08:45:52 GMT

Hi all,

I built a job in Talend for ESB v. 6.4.1. and it ran succesfully when running from the studio. Also when I deployed it in the task scheduler of my own PC (Windows 10, java build 1.8.0_45-b15) , but... It won't run when deployed in the same way at the server from where it should run. It's a Windows Server 2012, with the latest Java update build 1.8.0_162-b12.

I don't understand why it won't run properly, it doesn't throw errors or anything, it just doesn't start up. Even though it does say it has run afterwards.

And in the Task scheduler I just start the .bat file from the built job, the same way I do with other jobs, that are running just fine..

I hope someone has an idea what could be the problem!

Re: Built job doesn't run when deployed on Windows Server 2012

vapukov — Sat, 03 Feb 2018 03:34:34 GMT

the real reasons could be different of course, but ... but why You are not start from fix first difference:

- in many place highlighted - JDK version for studio and runtime must be the same?

what prevent You from upgrade JDK on Your machine?

unless not fix this - any other guess would be not correct

Re: Built job doesn't run when deployed on Windows Server 2012

Anonymous — Mon, 05 Feb 2018 08:38:17 GMT

Hello,

I upgraded the JDK on my machine, rebuilt and redeployed the jobs, but they still refuse to run at the server..

Any other ideas?

Re: Built job doesn't run when deployed on Windows Server 2012

vapukov — Mon, 05 Feb 2018 08:42:20 GMT

do You try run in it from CMD window? (not from explorer)

- open CMD window

- cd to Job folder

- run .bat file

what in print?

Re: Built job doesn't run when deployed on Windows Server 2012

Anonymous — Mon, 05 Feb 2018 08:56:01 GMT

Hmm.. the error is still that the java is not good, exactly:

Error: Registry key 'Software\JavaSoft\Java Runtime Environment'\CurrentVersion' has value '1.7', but '1.8' is required.

Error: Could not find java.dll

Error: Could not find Java SE Runtime Environmetn.

but it is installed on the server, if I check which version of java is running, it's the 1.8_162, now exactly the same as my own pc. Although there is also a 1.7 still running (for other talend jobs). Might that be the problem? How can i configure that this job should run with 1.8 ?

Re: Built job doesn't run when deployed on Windows Server 2012

vapukov — Mon, 05 Feb 2018 08:57:11 GMT

it mean - You have 2 or more installed on same server

You need remove old

You could check - what java run first

java -version
in same CMD window

You can edit PATH to and JAVA_HOME environment variables to be sure - what version they point
You can try to set all this variables inside .bat file

PATH = where proper JDK
JAVA_HOME=path to proper JDK

Re: Built job doesn't run when deployed on Windows Server 2012

Anonymous — Mon, 05 Feb 2018 08:59:57 GMT

That is not possible, because a lot of jobs are running on that server, which are built in other versions of java.

Re: Built job doesn't run when deployed on Windows Server 2012

vapukov — Mon, 05 Feb 2018 09:11:38 GMT

as I already suggest You - You can test add to variables

PATH

JAVA_HOME

to Your job .bat file

but generally - many versions of JAVA on same computer (especially Windows, where something store in registry) - it always source of collisions ...

so, The question - "why?", is resolved, and now You can decide - what todo

Re: Built job doesn't run when deployed on Windows Server 2012

Anonymous — Mon, 05 Feb 2018 09:29:50 GMT

It still doesn't work, even with the variables..

I keep getting the same error, which i posted before. Even when i just ask the java -version.

Re: Built job doesn't run when deployed on Windows Server 2012

vapukov — Mon, 05 Feb 2018 09:33:09 GMT

I keep getting the same error, which i posted before. Even when i just ask the java -version.

this is answer, if it production server - do not touch it! or You crash all job while try to resolve the problem!

Select new server dedicated to new task and migrate them 1 by 1 to java 1.8

Re: Built job doesn't run when deployed on Windows Server 2012

Anonymous — Mon, 05 Feb 2018 09:46:04 GMT

Well, it's our test server, so no danger there.

But i will discuss with others here whether i can delete the old version

Thanks anyway.

Re: Built job doesn't run when deployed on Windows Server 2012

Anonymous — Fri, 16 Feb 2018 10:22:22 GMT

We solved the issue by putting the compliance level of Java on 1.7, via View >> Preferences >> Java >> Compiler (see picture attached).

JavaComplienceLevel.png

Re: Built job doesn't run when deployed on Windows Server 2012

Anonymous — Fri, 07 Sep 2018 08:49:45 GMT

Is this 'Windows Server 2012' an aws -EC2 instance?