Error = 206 Classpath too long, even after full backup restore
Hi,
As the title says, I've started to get this error when I've moved Talend from Java SDK 8u91 to OpenJDK 8 (version 422 I think) for a Talend Remote Engine (v 2.11.11).
At first I thought it was a windows limitation so I've enabled long paths in the Group Policy editor, same issue. I have increased the memory of the Talend Remote Engine (-Xmx and -Xms), same error.
I've done a backup restore of the machine (back to Java SDK 8u91), from more than a month ago, I still have the issue, even though, when the machine was backed up, I was not getting this error. Also, my prod machines (same Java SDK 8u91) have not been touched and the same version of the task works perfectly.
I'm stuck, and I need a solution without the need to republish tasks (as I have over 100 of them). Can you please hel[?
This could be a problem with a known limitation from the Windows side.
As far as I know, long paths are not working for files executed by cmd.exe - regardless how you configure the system.
Please have a look at this parameter :CLASSPATH_SIZE_THRESHOLD" which helps to adjust the length so that long classpath strings can be dropped into a classpath.jar which will then be used as the classpath.
You could try to enable the long path and set the threshold(org.talend.remote.jobserver.commons.config.JobServerConfiguration.CLASSPATH_SIZE_THRESHOLD) to a lower value.
Unfortunately that doesn't help. I've tried multiple values (70 / 700 / 70000 / 700000). Still have the same issue.
There are two weird things here:
1. On different tasks I do no get this error. Only on the one.
2. Prod VMs don't have Enabled Long Paths, CLASSPATH_SIZE_THRESHOLD is 7000 (as it was on the QA VM that throws this error), same JAVA_OPTIONS, same task version, and I don't get this error.
The Job is running fine in the other environment you have? Could you please clarify what's talend product build version you are using?
We met a similar issue before in V 7.3.1 and it may be related to parent job trunjob with the large number of context variables + extra contexts that are added in the subjobwhen "Use an independent process to run" was checked.
The parameter 'Transmit whole context' if checked applies all the context variables of the main Job to the sub jobs. By unchecking it, only the necessary context variables for the sub job are applied.
Here is the reference about context variable related problem specific to windows
Could you please create a support ticket on our customer support portal so that we could give you a remote assistance through support cycle with priority?
