MuleSoft is adopting Java’s long-term-support (LTS) release cadence, beginning with Mule runtime 4.6, which adds support for Java 17 LTS.
This change has no immediate impact to Mule applications that are running on currently supported Mule versions, or on applications that are upgraded to Mule Runtime 4.6. Existing Java 8 apps will continue to run on Java 8 until August 2025 (End of Standard Support). For the latest information on Mule Runtime supported versions, refer to our documentation - Mule Runtime Release Cadence Support
Utilize this article and linked resources to ensure a smooth transition to Java 17 before August 2025.
Boosted Performance:
Java 17 introduces performance improvements such as quicker startup times, reduced garbage collection delays, and better handling of large applications.
Experience a noticeable enhancement in your application's performance.
Strengthened Security:
Java 17 brings critical security updates and fixes.
Upgrading means your applications are protected with the latest defenses against vulnerabilities.
Assured Long-Term Support:
Java 17 is an LTS release, offering extended support for a stable and reliable foundation, especially for enterprise applications with long lifecycles.
Strategize Your Upgrade:
Conduct an analysis of your current Mule 4.4 setup to pinpoint compatibility issues or deprecated elements.
Create a comprehensive upgrade plan, including testing, rollback strategies, and post-upgrade checks.
Schedule downtime and inform stakeholders to minimize business disruption.
Implementing the Upgrade:
Review MuleSoft's official documentation for upgrade guidance.
Test your integration flows, connectors, and APIs in a controlled environment before going live.
Work closely with your teams to manage the upgrade process effectively.
Check upgrade information for each product:
You can update, test, and redeploy most of your currently running Mule apps to use Java 17. However, any apps and connectors that are running custom Java code require additional work to certify those components. Before you upgrade your integration apps or Mule Gateway policies and proxies to Java 17, you must update all extensions, modules, and connectors used within those apps and policies to Java 17.
To ensure your API proxies or Mule apps are protected when upgrading, upgrade your API policies before upgrading your API proxies or Mule apps.
Thoroughly test all components to ensure they operate correctly after the upgrade.
Allow ample time for QA testing and involve stakeholders to confirm performance and functionality standards are met.
Watch this video for an overview of the runtime update and advice on upgrading to Java 17.
Anypoint Studio 7.17 – Easier Support for Java 17 - Read this blog to learn how Anypoint Studio 7.17 enhances support for Java 17, improving IDE stability and performance.
Upgrading Java for Policies and API Proxies - Refer to this documentation for steps to upgrade your policies and API proxies to be compatible with Java 17.
Java 17 specific Known Issues - Refer to this site for any Java 17 MuleSoft known issues.
#MuleSoftJava17Upgrade - Engage with the Trailblazer Community to ask questions and share insights about the Java 17 upgrade.
Java 17 Compatible Anypoint Connectors - Access this article for a comprehensive list of MuleSoft Anypoint connectors that are Java 17 compatible.
Upgrade Your Mule: Best Practices for Upgrading to Mule 4.6 - Follow this blog for best practices on upgrading to Mule 4.6, which fully supports Java 17 LTS.
Upgrading Java for Custom Connectors (Customers) - Refer to this documentation to upgrade, test, and release your custom connectors for Java 17 to ensure compatibility within the MuleSoft ecosystem.
Keeping your Mule versions up-to-date is vital for leveraging the full potential of your integration platform. Regular upgrades grant you access to the latest features, enhancements, and fixes, bolstering your system's performance and security. Stay compatible, reduce risks, and maintain a robust integration environment with MuleSoft.
002139151

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.