From RE v2.13 later on versions , you need to have JDK/JRE 17 as a must, but customers still need to keep compatibility with JDK 8 or 11.
Cause:
JDK 17 used as RE jump starter, Job execution and DataService still could use JDK 8 , 11 , 17 (which is configurable)(so for jdk 8/11 based customer, they have to keep 2 versions of jdk if they don't have plan updating to jdk 17 from studio/job design level)
https://help.talend.com/r/en-US/8.0/release-notes/r2023-09-remote-engine-upcoming-new-features
Talend Remote Engine v2.13 requires Java 17 to start, providing improved security of Java 17 and eliminating concerns about Java's end-of-support for older versions.
Importantly, although Java 17 is a mandatory requirement for the new engine to start,
when it comes to running Jobs or Microservices, you retain the flexibility to either use the default Java 17 version or choose older Java versions, through straightforward configuration of the engine.
Resolution:
Check the following etc folder based configuration and change it to installed jdk/jre path:
{
org.talend.ipaas.rt.dsrunner.cfg --> ms.custom.jre.path
org.talend.remote.jobserver.server.cfg --> org.talend.remote.jobserver.commons.config.JobServerConfiguration.JOB_LAUNCHER_PATH
}
