Skip to main content Skip to complementary content
Qlik Resources
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal

Using a more recent version of Java

Last updated: 9/10/2026
The best practice is to use Talend products with the most recent supported versions of Java.

Before you begin

Review the instructions to upgrade the Java version used by your products in Upgrading Java for all Talend services.

About this task

This procedure describes how to upgrade your Talend environment to use a more recent version of Java (Java 17 or Java 21).
Information noteTip: Java 21 support is available from Talend 8.0.1-R2026-06 and later.

Procedure

  1. Verify that your Talend Remote Engine and Talend JobServer instances support the Java versions to which you want to upgrade.
    The most recent versions of Talend Remote Engine and Talend JobServer require Java 17 or Java 21 for startup, but can also execute Jobs that use other Java versions.
    For further information about changing the Java version used for your engine or JobServer startup, see:
  2. Configure the JDK versions used by your Talend Remote Engine and Talend JobServer instances to ensure that all existing Jobs continue to run while upgrading to a more recent Java version (17 or 21). For each instance, set the JDK version to match the Java compatibility of each artifact:
    • If you have Jobs that require Java 8, configure Java 8 for those Jobs. For Jobs that are ready for Java 17 or Java 21, configure the appropriate Java version.
    • If all Jobs support Java 17 or Java 21, configure only that Java version.

    The above is the most common scenario to consider when configuring Java. For older versions, you may need multiple engine or JobServer instances running in parallel, each using a different Java version.

    However, the most recent Talend Remote Engine and Talend JobServer versions both support a dynamic JVM selection mode. This mode automatically selects the correct Java instance based on the Java compatibility level of the artifact to be executed. For instructions on configuring this JVM selection mode, see: This configuration allows you to run Jobs using different Java versions with a single engine or JobServer instance.
  3. If you are using Routes or Data Services, note that artifacts built as OSGi with Talend Studio R2025-02 or later are only compatible with Talend Runtime version 8.0.1-R2025-02-RT or later.
    • If you already built all of your Routes and Data Services as microservices with Talend 8.0, they can run with Java 11, Java 17, or Java 21. Routes and Data Services built from the R2025-02 release require at least Java 17 to run. Routes and Data Services built from R2026-06 can run with Java 21.
    • If you are using Routes or Data Services built as OSGi, you must install a Talend Runtime that uses Camel 4 from R2025-02. You must also install a new version of Talend Remote Engine if a Talend Remote Engine is part of your architecture. For more information, see Manual migration of a full Talend Runtime installation and Upgrading Talend Remote Engine.

      You can continue running your Camel 3 Talend Runtime and progressively rebuild and redeploy your Routes and Data Services to the new Talend Runtime that uses Camel 4 and that runs with Java 17 or Java 21. This is because Talend Runtime can handle only one Camel version, and Camel 4 is incompatible with Java versions below 17.

      Make sure to test and update any existing custom code or external libraries that you use in Routes and Data Services to ensure compatibility with Camel 4.

  4. Upgrade Talend Studio.
    If all your Jobs can run with Java 17 or Java 21, you can upgrade to a version of Talend Studio that builds and runs Jobs with Java 17 or Java 21.

    If some Jobs cannot run with the newer Java version, continue to use a Talend Studio version that supports building Jobs with Java 8, while progressively rebuilding all your Jobs with a more recent Java version (17 or 21) in another Talend Studio instance.

    Information noteImportant: Talend Studio versions that support Java 8 will be maintained for a limited time. If you are using Java 8, we recommend that you migrate to a more recent Java version (Java 17 or Java 21) as soon as possible to ensure continued support of your environment. Java 21 is the recommended Java version for Talend 8.0.1-R2026-06 and later.
  5. Rebuild artifacts progressively to make them natively run on a more recent Java version (Java 17 or Java 21).
    The best practice is to rebuild Routes and Data Services first, then rebuild frequently modified Jobs, and finally rebuild the remaining artifacts.
    By default, routines continue to be built with Java 8 compliance. You can upgrade routines to Java 17 or Java 21 if needed. Note that Big Data Jobs require routines compiled with a Java version compatible with the target cluster Java version. The flexibility of running routines with Java 8 accommodates big data technologies that do not yet support newer Java versions. For more information, see Setting the compiler compliance level.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here