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

Setting up the Java version to build artifacts in Talend Studio

You can configure the Java version used for compiling Routines and Jobs to match your target execution environment.

Procedure

  1. Click Project settings on the toolbar of the Talend Studio main window, or click File > Edit Project Properties from the menu bar to open the Project Settings dialog box.
  2. Expand the Build node and click Java Version to open the Java Version settings.
    Java Version configuration with Big Data features installed.

    The available settings depend on whether Big Data features are installed in Talend Studio:

    • Without Big Data features, the Java Version view shows the following settings:
      • Build Data Integration / Routes with: Java 17 or Java 21. Supported Java versions for runtime: Java 17 and Java 21.
      • Build User Routines with: Java 8, Java 17, or Java 21.
    • With Big Data features installed, the Java Version view shows two tabs:
      • Data integration / Routes: shows the same settings as the view without Big Data features.
      • Big Data: shows the Spark compilation options and supported Java versions for each Spark type:
        • Big Data Spark Batch < 3.5 / Streaming: compiled with Java 8 compliance only. Supported Java version for launcher: Java 17. Supported Java versions in cluster: 8, 11, and 17.
        • Big Data Spark Batch 3.5 and 3.x: compiled with Java 8 or Java 17 compliance. Supported Java versions for runtime: 17 and 21. Supported Java versions in cluster: 8, 11, and 17.
        • Big Data Spark Batch 4.0: compiled with Java 17 compliance only. Supported Java versions for launcher: 17 and 21. Supported Java versions in cluster: 17.
    Information noteNote: The Routine compilation level must not exceed the Job compilation level. If it does, Studio displays a warning listing the incompatible Job types.
  3. You can further configure the Java internal modules, for example to reduce the number of JVM warnings and fatal errors that occur when executing Jobs with Java 17 or Java 21.
    Click Module access settings under Java Version to open this view.
    • In the Default tab, you can view the Java internal modules for Talend components, the Talend Component Kit framework, and the Big Data distributions.
    • In the Custom tab, you can configure the Java internal modules for your custom components and the global Java internal modules for all Jobs and Routes.
    • When no Java internal module is configured for a given Job, you may get this kind of error:
      Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make field private static volatile java.net.Authenticator
                      java.net.Authenticator.theAuthenticator accessible: module java.base does not "opens java.net" to unnamed module @121f97fb
    • Jobs built by Talend Studio will have the --add-opens parameters in the job.sh or job.bat script files. For example:
      --add-opens=java.base/java.net=ALL-UNNAMED
    The --add-opens parameter is also added in the Java command for all the tRunJob components that are set up as independent.
  4. Click Apply and Close to apply your changes and close the dialog box.

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