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

[selimseddiki]

Dear support,

We have upgraded to remote engine 2.13.9 and enabled dynamic Java selection mode : https://help.qlik.com/talend/en-US/remote-engine-user-guide-windows/Cloud/configure-java-versions-fo...

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

We have enabled Java 17 compatibility in Talend studio 8 (8.0.1.20240920_1319-patch): https://help.qlik.com/talend/en-US/studio-user-guide/8.0-R2024-09/setting-compiler-compliance-level

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