help.salesforce.com Open in urlscan Pro
2a02:26f0:7100::687e:25a0  Public Scan

Form analysis
1 forms found in the DOM

POST

<form id="fileUploadForm" enctype="multipart/form-data" method="post" target="fileUploadIframe"><input type="file" id="fileSelector" name="file" style="display: none;"><input name="filename" type="hidden"></form>

Text Content

Loading
×Sorry to interrupt
CSS Error

Refresh
Industry Cloud managed packages mandatory upgrades (February 2024)Read More
Close


MULESOFT JAVA 17 UPGRADE FAQ

Publish Date: Nov 15, 2023
Description


WHY DO CUSTOMERS NEED TO UPGRADE TO JAVA 17?

With Trust as our number one value, MuleSoft is adopting Java’s
long-term-support (LTS) release, beginning with the Mule Runtime 4.6 which will
add support for Java 17 LTS. 

 

In addition to modernizing our stack, this decision comes in response to the
discontinuation of support for Java 8 by many third-party vendors, which will
have an impact on the MuleSoft product stack. Adopting this new release cadence
will provide greater security, compliance, and performance for our customers and
aligns with our core values of Customer Success and Trust.

 


WHEN WILL CUSTOMERS BE ABLE TO UPGRADE TO JAVA 17?

This transition begins with the Mule Runtime 4.6 release, which will support
both Java 8 and Java 17 LTS. Customers and partners should create a plan for how
they will transition from Java 8 to Java 17, with the ability to upgrade their
Mule applications and Mule gateway policies as early as Q1 2024. 

 

From a timeline perspective, we encourage customers and partners to undertake
Java 17 upgrading work in 2024 for these reasons:

 * Third party libraries used across the Anypoint platform will stop providing
   security patches as early as Dec 2024 – 2026 
 * Apps and policies that upgrade to Mule Runtime 4.9 (Feb 2025) will only
   support Java 17 and enables customers to leverage Java 17 capabilities  

 


IS THERE ANY IMMEDIATE IMPACT TO UPGRADING TO MULE RUNTIME 4.6?

This will have no immediate impact to Mule applications and Mule Gateway
policies and proxies that are running on currently supported Mule versions, or
on applications that are upgraded to Mule Runtime 4.6, as existing Java 8 apps
will continue to run on Java 8 while customers upgrade their apps and policies
to run on Java 17.

 

The following Runtime version support milestones should also help inform their
Java 17 upgrade planning in 2024 and beyond:

 
 1. Customers should take advantage of Mule 4.6 which supports Java 8 and 17 to
    plan their upgrade journey
 2. Strongly encourage customers to begin their migration journey in 2024
 3. Java 8 will supported by MuleSoft till Feb 2026
     

Mule Runtime Version

GA Date

Java Support

End of Standard Support

End of Extended Support

4.3

April 30, 2020

8

March 7, 2023

March 7, 2025

4.4

Sept 7, 2021

8

Oct 8, 2024

Oct 8, 2025

4.5 Edge

Oct 3, 2023

8

Feb 6, 2024

June 4, 2024

4.6 LTS (1)

Feb 6, 2024

8 and 17

Feb 4, 2025

Feb 3, 2026 (3)

4.6 Edge

Feb 6, 2024

8 and 17

June 4, 2024

Oct 8, 2024

4.7 Edge

June 4, 2024

8 and 17

Oct 8, 2024

Feb 4, 2025

4.8 Edge

Oct 8, 2024

8 and 17

Feb 4, 2025

June 3, 2025

4.9 LTS

Feb 4, 2025

17 

Feb 3, 2026

Feb 2, 2027

4.9 Edge 

Feb 4, 2025

17 

June 3, 2025

Oct 7, 2025



 


WHAT IS THE JAVA 11 END OF SUPPORT PLAN?

 

Along with the end of support for Java 8 with the Mule Runtime 4.9 release in
Feb 2025, Java 11 will also no longer be available. As such, customers need to
plan for their upgrade across both Java 8 and Java 11 apps. 

 


WHY IS MULESOFT NOT TARGETING JAVA 21, WHICH IS THE LATEST LTS?

Java 21 LTS was recently GA’d on September 21, 2023. As a result: 

 * Many third-party libraries have yet to announce a roadmap of when they will
   support Java 21. (E.g Scala only recently released a Java 21 compatible
   versions)
 * Java 21 removes support for key constructs on our stack which will need to
   accounted for ( e.g. Java 21 removes support for finalizers which Dataweave
   heavily relies on)
 * Waiting to adopt Java 21 would further delay the ability for customers to
   move away from Java 8 for security and compliance reasons.

 

The current projected plan for when Mule Runtime will adopt Java 21 is with Mule
Runtime 4.9 in Feb 2025, but these are not confirmed yet. 

 


WHICH MULESOFT PRODUCTS ARE IN SCOPE?

For Q1 2024 - Anypoint Platform

 * US and EU Commercial environments
   * Hybrid Standalone
   * CloudHub 1.0, CloudHub 2.0 and Runtime Fabric
 * US Gov Cloud (Feb 2024)
 * Anypoint Design to Deploy Tooling
   * Mule Runtime
   * Mule Agent, Anypoint Monitoring Agent 
   * Anypoint API Manager, Mule Gateway policies and proxies 
   * Anypoint Runtime Manager, Deployment APIs, Anypoint CLI, Mule Maven plugin
   * Connector Tooling (Mule SDK, XML SDK, REST Connect, Partner Certification
     tool)
   * Studio, MUnit

Post Q1 2024 

 * Private Cloud Edition (In planning)
 * MuleSoft managed experiences whereby MuleSoft will upgrade to Java 17 on
   behalf of customers
   * Composer
   * Anypoint Partner Manager
   * Dataloader.io
   * DataGraph
   * MuleSoft Direct

 


HOW WILL CUSTOMERS UPGRADE THEIR INTEGRATION APPS?

Anypoint Connectors

MuleSoft-built Anypoint connectors will be updated to Java 17 to enable
customers to easily upgrade where they have no app customizations. 

 

Mule SDK, XML SDK and REST Connect will be updated with Java 17 compatibility to
enable customers to update their custom connectors before they perform any app
upgrading.

 

Anypoint Design to testing to deploy

Anypoint Studio v7.17 will enable customers to change their projects’ intended
Java version, making it simpler to upgrade or downgrade the Java version of
their Studio projects. Studio will also provide automatic suggestions to upgrade
connectors to align with their projects’ intended Java version. 

 

During each stage of building and deploying applications, Anypoint Studio will
provide guidance. Whether a customer uses an incompatible connector or attempts
to deploy to an incompatible deployment environment, Studio will continuously
validate holistic Java compatibility and prompt customers with suggestions to
remediate.

 

MUnit will automatically inherit the intended Java version from a respective
Studio project. 

 

Anypoint Exchange will provide Java compatibility information for connectors,
allowing customers to identify Java 17-compatible connectors. 

 

Anypoint Runtime Manager will enable customers to choose the intended Java
version for deployments. The appropriate workers will automatically align with
the version customers choose.

 

APIs to deploy to CloudHub 1.0, CloudHub 2.0, and RTF will allow for specifying
a Java version. The Anypoint CLI will also accept an intended Java version tag
to help users deploy to the right environment.

 

Mule Maven Plugin will allow customers to choose their intended Java version for
deployments. 

 

Mule Gateway Policies and Proxies via Anypoint API Manager

Anypoint API Manager will enable customers to choose Java 8 or Java 17 for
deploying proxies and policies with guidance to simplify choosing the
appropriate policy and proxy. This includes MuleSoft providing customers with
updated Mule Gateway included policies and proxies that are Java 17 compatible. 

 


WHEN WILL CUSTOMERS BE ABLE TO START TAKING ACTION?

 

Java 17 upgrade planning starts with evaluating connectors, integration apps,
Mule Gateway policies, and proxies, as all of these components rely on Java. 

 

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 be Java 17-compatible first. 

 
 * MuleSoft will certify MuleSoft-built connectors to run on Java 17. 
   * Our most commonly used MuleSoft-built connectors will be ready by Q1 2024
     and others later in 2024. 
   * Once completed, customers can auto-detect and update apps with Java
     17-compatible Anypoint Connectors in Studio (April 2024). The app will then
     be Java 17-ready to be tested and deployed on your Mule Runtime 4.6+
     Runtime deployment environment.
      
 * Custom-built connectors will require customers and partners to update their
   own connectors. 
   * Effective February 2024 (Mule Runtime 4.6 GA), these updates can be made
     for connectors built using REST Connect, Mule SDK, or the XML SDK.
   * Once completed, test and deploy the updated app to run with Java 17 on your
     Mule Runtime 4.6+ runtime deployment environment. 

 

Upgrading Mule Gateway Policies and Proxies

 

MuleSoft will provide updated versions of Mule Gateway included policies and
proxies with Java 17 compatibility with the release of Mule Runtime 4.6 in
February 2024 for you to upgrade your API instances. These proxies and policies
will also still be Java 8 compatible. 

 
 * Custom policies will need to be updated with Java 17-compatible extensions
   and connectors before upgrading these policies in your API instance.
 * Custom proxies require re-deploying the underlying Mule apps that are updated
   with Java 17 connectors and components to your runtime deployment model. 

 


WHAT CAN CUSTOMERS AND PARTNERS DO BEFORE STUDIO V7.17 IS AVAILABLE IN APRIL
2024?

Mule Runtime 4.6 will be available in Feb while Studio v7.17 is expected to GA
at the end of March. 

 

Before Studio v7.17 is available, custom connectors can be upgrade:

 1. Begin upgrading custom connectors using the Mule/Java SDK, XML SDK and REST
    Connect with the Connector Upgrade Playbook.
 2. Partners with MuleSoft certified connectors can begin testing, certifying
    and publishing updated connectors  via Connector Asset Management tool (CAM)
    to Exchange. 

 

Once Studio is available, customers will have the end to end ability to:

 1. Upgrade / build / test locally and deploy apps in Java 17 
 2. Update existing custom Mule Gateway proxies to be Java 17 compatible to
    update their API instances with

 


WHEN WILL ANYPOINT CONNECTORS BE JAVA-17 COMPATIBLE AND HOW WILL CUSTOMERS AND
PARTNERS KNOW?

Mule Runtime 4.6 GA (Feb 2024)

 * A subset of available connectors will be Java 17 compatible, based on
   usage/adoption
 * Customers can determine which connectors are Java 17 compatible via product
   documentation and Anypoint Exchange connector listing

End of Q2 2024

 * Update remaining Anypoint Connectors

 


HOW AND WHEN WILL PARTNERS BE ABLE TO MAKE THEIR CONNECTORS JAVA-17 COMPATIBLE?

Mule Runtime 4.6 GA (Feb 2024)

 * Begin upgrading custom connectors using the Mule/Java SDK, XML SDK and REST
   Connect with the Connector Upgrade Playbook.
 * Partners with MuleSoft certified connectors can begin testing, certifying and
   publishing updated connectors  via Connector Asset Management tool (CAM) to
   Exchange.

 

For additional questions, please join the MuleSoft Salesforce Trailblazer
Community forum, where MuleSoft will continue to provide updates and
communications on this topic.  

Knowledge Article Number

000396936

Did this article solve your issue?
Let us know so we can improve!
YesNo
 
1-800-667-6389
 * 
 * 
 * 
 * 

SALESFORCE
 * Privacy Statement
 * Security Statement
 * Terms of Use
 * Participation Guidelines
 * Cookie Preference Center
 * Your Privacy Choices

COMMUNITY
 * AppExchange
 * Salesforce Admins
 * Salesforce Developers
 * Trailhead
 * Training
 * Trust

SUPPORT & SERVICES

Need help? Find more resources or connect with an expert.

Get Support

Powered by Experience Cloud

--------------------------------------------------------------------------------

© Copyright 2023 Salesforce, Inc. All rights reserved. Various trademarks held
by their respective owners.
Salesforce, Inc. Salesforce Tower, 415 Mission Street, 3rd Floor, San Francisco,
CA 94105, United States


English
Select Org
 * Select OrgEnglish
 * Français
 * Deutsch
 * Italiano
 * 日本語
 * Español (México)
 * Español
 * 中文（简体）
 * 中文（繁體）
 * 한국어
 * Русский
 * Português (Brasil)
 * Suomi
 * Dansk
 * Svenska
 * Nederlands
 * Norsk

Live chat:No Engineers Online


Loading

We use cookies on our website to improve website performance, to analyze website
usage and to tailor content and offers to your interests. Advertising and
functional cookies are only placed with your consent. By clicking “Accept All
Cookies”, you consent to us placing these cookies. By clicking “Do Not Accept”,
you reject the usage of such cookies. We always place required cookies, which
are necessary for the website to work properly. For more information about the
different cookies we are using, read the Privacy Statement. To change your
cookie settings and preferences, click the Cookie Consent Manager button.
Do Not Accept Accept All Cookies
Cookie Consent Manager



COOKIE CONSENT MANAGER




 * GENERAL INFORMATION


 * REQUIRED COOKIES


 * FUNCTIONAL COOKIES


 * ADVERTISING COOKIES

GENERAL INFORMATION

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

Always Active

Required cookies are necessary for basic website functionality. Some examples
include: session cookies needed to transmit the website, authentication cookies,
and security cookies.

Cookies Details‎

FUNCTIONAL COOKIES

Functional 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.

Cookies Details‎

ADVERTISING COOKIES

Advertising Cookies


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.

Cookies Details‎
Back Button


COOKIE LIST

Filter Button
Consent Leg.Interest
checkbox label label
checkbox label label
checkbox label label

Clear
checkbox label label
Apply Cancel
Save Settings
Accept All Cookies