Java 17 compatibility enabled in studio, engine 2.13.9 set with dynamic Java selection, but job still runs under Java 8

selimseddiki — Thu, 30 Jan 2025 20:32:36 GMT

Dear support,

In file <RE_installation>/etc/system.properties, we have set the 2 variables:

org.talend.execution.JAVA_8_PATH=path to Java 8 bin directory

org.talend.execution.JAVA_17_PATH=patch to Java 17 bin directory

Nevertheless, after redeploying an artifact, it seems to be still running under Java 8. In the execution logs on TMC I see :

job XXX execution from task execution XXX started using Java 8 on path C:/Program Files/Java/jre1.8.0_291/bin

Was it not supposed to use Java 17 for execution ?

Thank you

topic Java 17 compatibility enabled in studio, engine 2.13.9 set with dynamic Java selection, but job still runs under Java 8 in Installing and Upgrading