Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
A Job fails to run on a remote JobServer with the following error message:
Unrecognized option: --add-opens=java.base/java.lang=ALL-UNNAMED
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Cause
The issue occurs with Talend Remote Engine or Talend JobServer using Java 8, but Talend Studio has JDK 17 enabled. The --add-opens option is only supported in java 11 and above, Java 8 does not support it.
If the 'Enable Java 17 compatibility' option is enabled, the Jobs built by Talend Studio will have the --add-opens parameters in the job.sh or job.bat script files, such as:
JAVA_OPTS=-Dfile.encoding=UTF-8 -Dsun.stdout.encoding=UTF-8 -Dsun.stderr.encoding=UTF-8 -Dconsole.encoding=UTF-8 --add-opens=java.base/java.lang=ALL-UNNAMED
The Jobs built this way cannot be executed with Java 8.
Resolution
Option 1:
- Click
on the toolbar of Talend Studio main window, or click File > Edit Project Properties from the menu bar to open the Project Settings dialog box.
- Expand the Build node and click Java Version to open the corresponding view.
- Deactivate the 'Enable Java 17 compatibility' option.
- Re-build the Job and re-publish it to Talend Remote Engine or Talend JobServer.
Option 2:
From R2024-05, Java 17 will become the only supported version to start most Talend modules, If you want to keep the "Enable JAVA 17 Compatibility" option enabled, make sure that Talend Remote Engine or Talend JobServer also uses JDK 17 to execute jobs.
For Java Option Command --add-opens, using SPACE or = depends on OS, JDK version or the place where you setup, there are 3 cases:
1. support both SPACE and =
2. support SPACE only
3. support = only
Example:
--add-opens=java.base/java.net=ALL-UNNAMED
--add-opens java.base/java.net=ALL-UNNAMED
Related Content
Setting-compiler-compliance-level
