Java Adoption
Starting with Mule runtime engine 4.6, MuleSoft is adopting Java’s long-term support (LTS) release cadence, which adds support for Java 17 LTS.
Mule Runtime Java Support
The following table shows the timeline for Java 8 and Java 17 support:
| Mule Version | Release Date | Java Version | End of Standard Support | End of Extended Support |
|---|---|---|---|---|
4.8 Edge |
October 2024 |
8, 11, and 17 |
March 2025 |
June 2025 |
4.7 Edge |
June 2024 |
8, 11, and 17 |
October 2024 |
February 2025 |
4.6 LTS |
February 2024 |
8, 11, and 17 |
August 2025 |
February 2026 |
4.6 Edge |
February 2024 |
8, 11, and 17 |
June 2024 |
October 2024 |
4.5 Edge |
October 2023 |
8 and 11 |
February 2024 |
June 2024 |
4.4 |
September 2021 |
8 and 11 |
October 2024 |
October 2025 |
4.3 |
April 2020 |
8 and 11 |
March 2023 |
March 2025 |
Java 17 is recommended. The change has no immediate impact on Mule applications and Mule Gateway policies and proxies running on currently supported Mule versions, or on applications upgraded to Mule runtime 4.6. Mule apps that are currently running on Java 8 continue to be supported until February 2026. Support for Java 8 ends with the Mule runtime 4.9 release in February 2025, and Java 11 will no longer be available.
For more information about the Java adoption, see Java Support
Upgrading Mule Apps
| Before you upgrade your integration apps or Mule Gateway policies and proxies to Java 17, all extensions, modules, and connectors used within those apps and policies must first be Java 17-compatible. |
Components (custom code, custom connectors, MuleSoft connectors) are now Java 17-compatible. Test and redeploy your apps to run with Java 17 on your runtime deployment model. If your app doesn’t have custom code, you can add Java-17 connectors to your app through Studio as usual. After apps are updated and Java 17-ready, test them in your Mule 4.6 and later runtime deployment environment.
Mule Gateway API policies and proxies are now Java 17-compatible, so you can upgrade your API instances.