Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
I had a project on Talend Data Integration 6.1 working perfectly;
Due a problem in the machine, I needed to recreate the environment in a new machine so I have downloaded Talend Data Integration 7.1, I have downloaded java jdk1.8.0_212 and set up JAVA_HOME to "<C:\Program Files\Java\jdk1.8.0_212>" and ;%JAVA_HOME%\bin in within path variable
in a SubJob I have a tRunJob_1 with Use dynamic job selected; now everytiem I debug the project I get the following error:
java.io.IOException: Cannot run program "<C:\Program Files\Java\jdk1.8.0_212\jre\bin\java.exe>": CreateProcess error=206, The filename or extension is too long
I have try following solutions:
Move Java folder to E:, changing all environment variables:
Exception in component tRunJob_1 (PassiveData_Parent_Job)
java.lang.RuntimeException: Child job running failed.
java.io.IOException: Cannot run program "E:/jdk1.8.0_212/jre/bin/java.exe": CreateProcess error=206, The filename or extension is too long
at reflectedlife_newbernard.passivedata_parent_job_0_1.PassiveData_Parent_Job.tRunJob_1Process(PassiveData_Parent_Job.java:2991)
at reflectedlife_newbernard.passivedata_parent_job_0_1.PassiveData_Parent_Job.tPostgresqlRow_6Process(PassiveData_Parent_Job.java:2668)
at reflectedlife_newbernard.passivedata_parent_job_0_1.PassiveData_Parent_Job.tPostgresqlInput_1Process(PassiveData_Parent_Job.java:2340)
at reflectedlife_newbernard.passivedata_parent_job_0_1.PassiveData_Parent_Job.runJobInTOS(PassiveData_Parent_Job.java:5170)
at reflectedlife_newbernard.passivedata_parent_job_0_1.PassiveData_Parent_Job.main(PassiveData_Parent_Job.java:4802)
I found this in StackOverflow https://stackoverflow.com/questions/10519558/createprocess-error-206-the-filename-or-extension-is-to...
I try to set up the accepted answer update, but I can not find where to set up useexternalfile="yes" in talend:
I also try this comment (in the same accepted answer)
"Reduce the classpath" is a nice hint, but let me elaborate a little bit on this: In my case, I tried to build a maven project, and the -classpath argument was generated to contain all the dependencies. So, something like this came out: C:\Users\myself\.m2\repository\…;C:\Users\myself\.m2\repository\…[…tons more]. Moving my local maven repo cache to D:\m2 did the trick: Classpath shrank down to D:\m2\…;D:\m2\… - bingo! Remember to set the localRepository path in your maven config
to try that:
I have copied C:\Talend\TOS_DI-Win32-20181026_1147-V7.1.1\configuration\.m2 into E drive:
then in talend: window -->preference-->Maven-->UserPreference update settings and change localRepository to E:\.m2\repository
I am still receiving the same java error.
Thanks very much for your help
I make my project works reviewing all context variables passed to tRunJob. I delete the ones weren't used (legacy code); but the main problem still stands,
Why in previous versions of Talend was working and in this one I needed to clean those variables?
Hello,
If not selecting "use an independent process to run subjob" in tRunJob, does it work within studio?
Best regards
Sabrina
Hi Sabrina,
Thanks for your answer.
Sorry, Setting the job as "use an independent process to run subjob" didn't work. I get the same error
Starting job PassiveData_Data_Load at 09:38 30/05/2019.
Null value will be used for context parameter PassiveData_App_Client_Status_Header: For input string: ""
[statistics] connecting to socket on port 3505
[statistics] connected
Exception in component tRunJob_1 (PassiveData_Data_Load)
java.io.IOException: Cannot run program "E:/jdk1.8.0_212/jre/bin/java.exe": CreateProcess error=206, The filename or extension is too long
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
at java.lang.Runtime.exec(Runtime.java:620)
at java.lang.Runtime.exec(Runtime.java:485)
at tt.passivedata_data_load_0_1.PassiveData_Data_Load.tRunJob_1Process(PassiveData_Data_Load.java:7190)
at tt.passivedata_data_load_0_1.PassiveData_Data_Load.tPostgresqlInput_1Process(PassiveData_Data_Load.java:4969)
at tt.passivedata_data_load_0_1.PassiveData_Data_Load.runJobInTOS(PassiveData_Data_Load.java:10492)
at tt.passivedata_data_load_0_1.PassiveData_Data_Load.main(PassiveData_Data_Load.java:7578)
Caused by: java.io.IOException: CreateProcess error=206, The filename or extension is too long
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(ProcessImpl.java:386)
at java.lang.ProcessImpl.start(ProcessImpl.java:137)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
... 6 more
[statistics] disconnected
Job PassiveData_Data_Load ended at 09:38 30/05/2019. [exit code=1]
Hello,
Did you get this issue only on Window server? Have you tried JDK 1.8 instead of JRE?
Best regards
Sabrina
Hello Sabrina,
What you mean with "only on Window server?" I am running Talend in a windows machine... i don't have any other OS available....
"Have you tried JDK 1.8 instead of JRE?"
as far as I have set up everything in windows, I believe I am using JDK 1.8 not JRE, although it is true when the error is display it says:
"E:/jdk1.8.0_212/jre/bin/java.exe" is that what you mean? How can I change that? my windows environment variables are:
users variables
JAVA_HOME:E:\jdk1.8.0_212
path:E:\jdk1.8.0_212\bin
System variables:
JAVA_HOME:E:\jdk1.8.0_212
path:E:\jdk1.8.0_212\bin
also I have added the following line into TOS_DI-win-x86_64.ini
I make my project works reviewing all context variables passed to tRunJob. I delete the ones weren't used (legacy code); but the main problem still stands,
Why in previous versions of Talend was working and in this one I needed to clean those variables?
I am getting same error, how do we resolve this? The number of context variable pass to subjob is also less and when i uncheck the subjob as independent process it works fine. Please help resolve this.
Hello,
Could you please clarify in which Talend version/edition you are?
Best regards
Sabrina
Talend Studio 7.3.1. The same job with same setup works in 6.3.
Hello,
We need more information to address your issue.
Are you encountering this issue when passing a large number of contexts in job? Is issue with running the job locally from Studio?
Best regards
Sabrina