Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Data Works for AI is here - Join the discussion and enter to win a pair of Qlik kicks: Join the Conversation!
Sonja_Bauernfeind
Digital Support
Digital Support

To all Talend customers,

This is an advance notice that, to enhance both your security and experience, Java 21 will be required to launch Talend Studio starting with the 2026-06 release.

This change only concerns the Talend Studio desktop application. It has no impact on the Jobs and Services you build with it, which will continue being compliant with Java 17 runtime environments (and Java 8 for Big Data Jobs).

 

You have multiple options to make a smooth transition:

  • The Talend Studio embedded upgrade mechanism (Feature Manager) will offer handling the JDK version upgrade
  • Should you prefer, a new installer of Talend Studio 2026-06 with JDK 21 embedded will also be provided
  • You will also be free to manually configure Talend Studio to start with JDK 21, provided you are on Talend Studio 2025-09 or higher

 

Additional details:

Along with this change, the June release will come with many additions from a Java version perspective:

  • Talend Studio will allow building Jobs and Services for Java 21 runtimes, in addition to Java 17 runtimes. Java 17 will remain the default setup for runtimes for the time being
  • Remote Engines, Cloud Engines, Dynamic Engines, Job Server, and Talend Runtime will support running Jobs and Services in Java 21, in addition to the Java versions they already support
  • Talend Administration Center (TAC), Data Preparation (client-managed), Data Stewardship (client-managed), Talend SAP RFC Server, Talend Semantic Dictionary, and Talend Identity and Access Management will also support running with Java 21 in addition to Java 17

 

For further questions, please start a chat with us to contact Qlik Support and subscribe to the Support Blog for future updates.

 

Thank you for choosing Qlik,
Qlik Support

15 Comments
yfujioka
Partner - Creator
Partner - Creator

こんにちは

Java17でビルドしたジョブはJava21のJobserver、REでそのまま動きますか。
Java21のJobserver、REで動かすためTalend Studio(Java21)で再ビルドが必要になるのでしょうか。

よろしくお願い致します。

0 Likes
2,563 Views
ameyniel
Contributor
Contributor

Hello,

Most of the Jobs compiled with Java 17 compliance should run as is in a Java 21 runtime (Job Server or RE). But this is indeed dependent on what your Jobs are doing.

Should you need to fix them, the version of Studio to choose only depends on the compliance version you want to build your Jobs with. Typically, in some cases, it is possible to fix a Job that does not work in a Java 21 runtime while still compiling it with Java 17 compliance.

Hope this helps.

 

0 Likes
2,363 Views
yfujioka
Partner - Creator
Partner - Creator

こんにちは

Java 21でのジョブとサービスの実行をサポートします。と記載がありますが、JobserverとTACはどの累積パッチからJava 21をサポートしておりますでしょうか。


また、TAC、JobserverでJava21をサポートしている場合、以下のドキュメントの修正をお願いいたします。
https://help.qlik.com/talend/en-US/installation-guide-linux/8.0/compatible-java-environments?ver=14


よろしくお願いいたします。

0 Likes
1,115 Views
Abdelrhman_Mohamed
Partner - Contributor II
Partner - Contributor II

Hello,

I upgraded Talend Studio and choose the "a new installer of Talend Studio 2026-06 with JDK 21 embedded" option to let the installer handle installing JAVA 21.

Abdelrhman_Mohamed_0-1782390484344.png

 

But when it finished and tried to run it, I got this message as shown in the screenshot.

Screenshot 2026-06-25 141324.png

Could you explain how to run Studio normally using JAVA 21?

Regards,

Abdelrhman

0 Likes
968 Views
LDR
Creator II
Creator II

Hi to everyone,

I also would like to be sure if once we have applied the update R2026-06 any new job will use Java 21, and therefore I will need to update also my remote engines to be able to run those new Java 21 jobs.

Can anyone confirm me it?

Thanks in advance

0 Likes
906 Views
LDR
Creator II
Creator II

Hi @Abdelrhman_Mohamed 

I just have updated my TS from release R2026-05 to R2026-06, and it runs without any error. I would say that I have followed the same steps than you, so maybe you can do some of the following options:

  • To run a fresh intallation and update. I know it requires more time but it's an option.
  • To check the content of the file <Talend-Studio-win-x86_64.ini>. In my case it contains the following lines:

-vm
plugins/org.eclipse.justj.openjdk.hotspot.jre.full.stripped.win32.x86_64_21.0.10.v20260205-0638/jre/bin
-vmargs
-Xms512m
-Xmx1536m
-Dfile.encoding=UTF-8
-XX:+UseG1GC
-XX:+UseStringDeduplication
-XX:MaxMetaspaceSize=512m
--add-modules=ALL-SYSTEM
--add-opens=java.base/java.lang=ALL-UNNAMED
--add-opens=java.base/java.util=ALL-UNNAMED
--add-opens=java.base/java.io=ALL-UNNAMED
--add-opens=java.base/java.util.stream=ALL-UNNAMED
--add-opens=java.base/java.util.regex=ALL-UNNAMED
--add-opens=java.base/java.lang.invoke=ALL-UNNAMED
--add-opens=java.base/java.lang.reflect=ALL-UNNAMED
--add-opens=java.base/java.net=ALL-UNNAMED
--add-opens=java.base/java.nio=ALL-UNNAMED
--add-opens=java.base/java.util.concurrent=ALL-UNNAMED
--add-opens=java.base/sun.nio.ch=ALL-UNNAMED
--add-opens=java.base/sun.nio.cs=ALL-UNNAMED
--add-opens=java.base/sun.security.action=ALL-UNNAMED
--add-opens=java.base/sun.security.pkcs=ALL-UNNAMED
--add-opens=java.base/sun.security.x509=ALL-UNNAMED
--add-opens=java.base/sun.util.calendar=ALL-UNNAMED
--add-opens=java.security.jgss/sun.security.krb5=ALL-UNNAMED
--add-opens=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED
-XX:CompileCommand=quiet
-XX:CompileCommand=exclude org.eclipse.jdt.internal.core.dom.rewrite.ASTRewriteAnalyzer::getExtendedRange
-Dosgi.requiredJavaVersion=21
-Ddraw2d.enableAutoscale=false
-Dswt.autoScale.updateOnRuntime=false

Get luck!

879 Views
Sonja_Bauernfeind
Digital Support
Digital Support

@yfujioka TAC (R2026-01) and Jobserver (R2025-12) can support JAVA 21. Talend Runtime supports Java 21 from the 8.0.1-R2026-05 release 

@Abdelrhman_Mohamed a case might be needed to investigate this, but I am still looking for advice for you.

@LDR Finding an answer for you!

All the best,
Sonja 

 

 

842 Views
Sonja_Bauernfeind
Digital Support
Digital Support

Hello @Abdelrhman_Mohamed, I've confirmed that the best way forward on this would be to open a support case (should you not have been able to resolve it based on LDR's recommendations). When you do so, include the Studio logs from the workspace/.metadata folder. File is called ".log"

@LDR Not necessary, you can select the Java version compatibility. Example:

image.png

 

All the best,
Sonja 

 

791 Views
Abdelrhman_Mohamed
Partner - Contributor II
Partner - Contributor II

Hello @Sonja_Bauernfeind,

Thanks for getting back to me.

I tried the configuration that @LDR shared (@LDR thanks for that BTW), and its open TS but the compiler opens too and stays open. If I tried to close the compiler, TS closes too.

I don't think this is the best solution in my case, specially that JAVA 21 is not installed properly and is not configured automatically in the .ini file despite following the right steps.

I will try to open a case to find out where the right java 21 file is located.

Best,

Abdelrhman

0 Likes
719 Views
JCLamoure
Support
Support

Hello @Abdelrhman_Mohamed ,

 

you may verify that java 21 has been properly installed during the upgrade : 

 

java21 is located in : 

<studio install directory> \studio\plugins\org.eclipse.justj.openjdk.hotspot.jre.full.stripped.win32.x86_64_21.0.10.v20260205-0638

and should contains : 

2026-06-28_09h53_39.png

 

then the .ini file should have the -vm parameter pointing to it as  @LDR pointed out.

2026-06-28_09h57_16.png

Also note that the path should not contains a space.

https://help.qlik.com/talend/en-US/installation-guide-windows/8.0/installing-archive

otherwise the update of the .ini will fails and the studio logs will contains message like :

WARN  org.talend.studiolite.p2.api.P2Util  - Failed to read -vm from .ini: Cannot invoke "java.io.File.toPath()" because "iniFile" is null

best,

 

700 Views