Oracle stops the active support of Java 11 in September 2023. It has consequences on the TIBCO EBX product, but this may also have an impact on your TIBCO EBX projects.

On the TIBCO EBX product side:

• The compilation will remain with JDK 8 (for versions 5.9.x and 6.0.x) and JDK 11 (for versions 6.1.x and above).

• The EBX test platform reference will be upgraded from JDK 11 to JDK 17 for all releases after October 2023, but the automated tests on JDK 11 will still be used for all releases. 

On your side:

• We suggest you to upgrade your application server to a Java 17 compatible version

What are the consequences if you don’t migrate?

If you are facing a bug, it may be related to Java 11. As this Java version is not supported anymore, our support team will use Java 17, meaning that it’s possible that you can be asked to replicate the case on a supported Java version. 

Which application servers should you use ?

• If you are using TIBCO EBX 5.9.x, from the upcoming 5.9.25 service pack release :

  1. WebLogic 14c: see the point on WebLogic

  2. WebSphere AS 9 (deprecated) should be upgraded to WebSphere Liberty 23

  3. JBoss 7.1 should be upgraded to JBoss 7.4 Update 8

  4. Tomcat 8.x should be upgraded to Tomcat 9.x

• If you are using TIBCO EBX 6.0.x :

  1. WebLogic 14c: see the point on WebLogic

  2. WebSphere Liberty 23 (Already compatible)

  3. JBoss 7.1 should be upgraded to JBoss 7.4 Update 8

  4. Tomcat 9.x (Already compatible)

• If you are using TIBCO EBX 6.1.x, from the upcoming 6.1.3 service pack release :

  1. WebLogic 14c: see the point on WebLogic

  2. WebSphere Liberty 23 (Already compatible)

  3. JBoss 7.4 Update 8 (Already compatible)

  4. Tomcat 9.x (Already compatible)

Note on WebLogic:

WebLogic 14c supports Java 11. The first version to support Java 17 will be the 14.1.2, planned for 2024. Consequently, EBX will continue to support WebLogic 14c with Java 11. Please note that version 14.1.2 will only support Jakarta 8 which surely conflicts with future versions of EBX (6.2.x or any version where third party library upgrade requires Jakarta 9 or above).
For all these reasons, we strongly encourage you to move to a different application server as EBX may no longer support it.

Other changes

5.9.x change

Due to an upgrade of a third party library, to support JDK 17, the previous URI default JSON serialization suffered from asymmetrical representation. URI are no longer serialized as JSON objects but as String values. This change restores a uniform behavior when URI are:

• Used as Java method returned value.
• Held in collections.
• Stored in DTO objects.

Display policy

The Unicode CLDR (Common Locale Data Repository) has changed with JRE versions and impacts locale sensitive formats such as integer or decimal. By default, EBX uses the JRE’s native format, but you can configure this option and have a compatible/different result if needed.

Container Edition

The JDK in Container Edition has been upgraded from JDK 11 to JDK 17 in version 6.0.17.

All these changes will be specified into the release notes of the various EBX releases.

• Oracle Java SE Support Roadmap : https://www.oracle.com/java/technologies/java-se-support-roadmap.html