Java Requirements
All components of Tungsten are certified with Java using the following versions:
8
11
17 (Tungsten versions 7.1.4 onwards only)
21 (Tungsten versions 8.0.0 onwards only)
Java 9, 10 and 13 have been tested and validated but certification and support will only cover Long Term releases.
Please do NOT upgrade to the following specific versions of Java that were released on January 20th, 2026, if your deployment has security enabled:
25.0.2
21.0.10+8
17.0.18+8
11.0.30+7
1.8.0_481-b10
Environments without security enabled are not impacted.
These Java releases introduce a change to the default behavior of RMI communication, which is critical for internal communication between Tungsten components. In security-enabled deployments, this change prevents components from operating correctly.
All Java versions prior to those listed above are safe and unaffected.
If an upgrade is required, we strongly recommend postponing it until a patch is released to mitigate the issue. For further clarification or guidance, please contact us through the usual support channels.
Internal Bug Reference: CT-2666
There are a number of known issues in earlier Java revisions that may cause performance degradation, high CPU, and/or component hangs, specifically when SSL is enabled. It is strongly advised that you ensure your Java version is one of the following MINIMUM releases:
Oracle JRE 8 Build 261
OpenJDK 8 Build 222
Oracle JRE 11 Build 8
All versions from 8u265, excluding version 13 onwards, contain a bug that can trigger unusually high CPU and/or
system timeouts and hangs within the SSL protocol. To avoid this, you should add the following entry to the wrapper.conf
file for all relevant components. This is included by default from version 6.1.15 onwards of all Tungsten products.
wrapper.conf can be found in the following path <INSTALLDIR>/tungsten/tungsten-component/conf,
for example: /opt/continuent/tungsten/tungsten-manager/conf
wrapper.java.additional.{next available number}=-Djdk.tls.acknowledgeCloseNotify=true
For example:
wrapper.java.additional.16=-Djdk.tls.acknowledgeCloseNotify=true
After editing the file, each component will need restarting
If your original installation was performed with Java 8 installed, and you wish to upgrade to Java 11, you will need
to issue tools/tpm update --replace-release on all nodes from within the software staging path.
This is to allow the components to detect the newer Java version and adjust to avoid calls to functions that were deprecated/renamed between version 8 and version 11.