Mule Runtime 3.9 End of Extended Support and End of Life

Mule 3.9 will reach its End of Life (EOL) on March 20th, 2024. This follows MuleSoft’s Product Versioning and Back Support Policy. MuleSoft will provide EOL Support for On Premise applications until March 20th, 2025.

If you are still using Mule runtime version 3.9 or any of its patch versions, we encourage you to upgrade to Mule runtime 4.4 or later, the latest patch version available, as soon as possible. Please work with your Account Team if you need assistance with this transition.

To summarize:

Runtime Version	End of Standard Support	End of Extended Support
3.9	March 20th, 2021 (Completed)	March 20th, 2024

What is the important Mule 3.9 EOL reminder about?

Products that are not covered by Standard Support or Extended Support are considered EOL. After the EOL support period expires for a product, MuleSoft will not provide support of any kind. For more details on a) Standard Support, b) Extended Support and c) EOL support, read the Product Versioning and Back support policy. Please refer to your deployment model for specifics on EOL support below.

CloudHub / CloudHub 2.0

Please refer to the table below for specific behaviors with your Sandbox and Production apps to both Sandbox and Production apps on 3.9 in CloudHub:

TYPE

DATE

SANDBOX/PRODUCTION

Mule 3.9 During EoES

Until March 20th, 2024

Customers can deploy new apps?: No.
Customers can restart existing apps?: Yes.
Customers can deploy updated versions of existing apps on 3.9 runtimes?: Yes.
MuleSoft will interrupt and stop running apps in this deprecated release?: No

Mule 3.9

After EOL

On March 20th, 2024

MuleSoft will recurrently interrupt and stop running apps in this deprecated release?: Yes.

Runtime Fabric

Please refer to the table below for what will happen to both Sandbox and Production apps on 3.9 in Runtime Fabric:

TYPE	DATE	SANDBOX/PRODUCTION
Mule 3.9 During EoES	Until March 20th, 2024	Customers can restart existing apps?: Yes. Customers can deploy updated versions of existing apps on 3.9 runtimes?: Yes. MuleSoft will interrupt and stop running apps in this deprecated release?: No. Customers can deploy new apps?: Yes.
Mule 3.9 After EoES	After March 20th, 2024	Customers can restart existing apps?: Yes. Customers can deploy updated versions of existing apps on 3.9 runtimes?: Yes. MuleSoft will interrupt and stop running apps in this deprecated release?: No. (Mule Runtimes will keep running locally on the environment they were deployed to under customer’s responsibility without support) Customers can deploy new apps?: No. Customers can change the patch versions within the mule runtime minor version such as from 3.9.x to 3.9.y? : No

MuleSoft-managed customer-hosted runtimes registered through Anypoint Runtime Manager

Please refer to the table below for what will happen to both Sandbox and Production apps on Mule Runtime 3.9 on customer-hosted runtimes:

TYPE	DATE	SANDBOX/PRODUCTION
Mule 3.9 During EoES	Until March 20th, 2024	Customers can restart existing apps?: Yes. Customers can deploy updated versions of existing apps on 3.9 runtimes?: Yes. MuleSoft will interrupt and stop running apps in this deprecated release?: No. Customers can deploy new apps?: Yes.
Mule 3.9 After EoES	After March 20th, 2024	Customers can restart existing apps?: Yes. Customers can deploy updated versions of existing apps on 3.9 runtimes?: Yes. (through Runtime Manager during End of Life Support and deploying application files directly to the local installation) MuleSoft will interrupt and stop running apps in this deprecated release?: No. (Mule Runtimes will keep running locally on the environment they were deployed to under customer’s responsibility without support) Customers can deploy new apps?: Yes. (through Runtime Manager during End of Life Support and deploying application files directly to the local installation) Please Note: MuleSoft reserves the right to terminate connections between the on-prem deployment and the cloud control plane after End of Extended support to protect against vulnerabilities

As part of the Mule 3.9 End of Life, the following component versions are not backward compatible with Mule 4.x and accordingly will no longer be supported.

RETIRING FEATURE/ VERSION	REPLACEMENT FEATURE/ VERSION	DESCRIPTION
Anypoint Studio 6	Anypoint Studio 7	Customers will need to perform the 2 steps listed below: Install Studio 7 Use this document to migrate all projects from Mule 3 to Mule 4.
MUnit 1	MUnit 2	As part of the migration to Mule 4.x, customers who migrate their projects to Studio 7 will automatically get access to MUnit 2. No additional steps need to be taken for MUnit.
Mule Maven Plugin 2	Mule Maven Plugin 4	As part of the migration to Mule 4.x, customers who migrate their projects to Studio 7 will automatically get access to Mule Maven Plugin 3. No additional steps need to be taken for Mule Maven Plugin.
DataMapper	DataWeave	Customers can use the migration tool included in Studio which can be used to migrate DataMapper maps to DataWeave.
Runtime Manager (Runtime Manager Agent v 1.x)	Runtime Manager (Runtime Manager Agent v 2.x)	The Runtime Manager will continue to work as expected. [For only On-prem customers, here is the document to upgrade the Runtime Manager Agent to 2.x version]
API Manager (APIs with unclassified environment)	Environments in API Manager	Customers need to classify APIs into an Environment before they can migrate those APIs from Mule 3 to 4. Use this document to classify APIs into an Environment
Anypoint Monitoring	Anypoint Monitoring	The Anypoint Monitoring will continue to work as expected. Only for On-prem customers, here is the document to upgrade to the latest Anypoint Monitoring agent. However, all Monitoring Agent versions support Mule 3 and Mule 4.
Connector DevKit	Mule SDK	DevKit is compatible only with Studio 6 and Mule 3. To build Mule 4 connectors, see the Mule SDK documentation. And to migrate Mule 3 DevKit connectors to Mule 4 SDK connectors, see this DevKit Migration Tool.

What will happen after March 20, 2024?

Apps running in a CloudHub environment will shutdown and no longer be accessible or available after March 20, 2024.
Apps (3.9.x) running in a CloudHub environment will experience more frequent shutdowns. Be note that we do not disclose the shutdown schedule to customers. Please reach out to your account manager to plan the 3.9 apps migration.

What will happen after March 20, 2025?

Mule 3.9 will be completely unsupported after this date, even if applications continue to run.
To avoid any operational disruption, MuleSoft does not plan to terminate on-prem Mule 3.9 runtimes from connecting to Anypoint Platform services such as Runtime Manager, API Manager, Gateway, API Designer/Console, application logs, and Anypoint Monitoring. However we reserve the right to terminate connections between the on-prem deployment and the cloud control plane at any time beyond March 20, 2025 (for example, to protect against future vulnerabilities).

What action do I need to take?

Depending on the deployment model you are using, please note the EOL deadlines and associated support for administration actions.
Familiarize yourself with the documentation and resources outlined above.
Work with your Account Team to start planning the migration to Mule 4.4 (latest patch available) ahead of the 3.9 EOL deadline (March 20, 2024).

Please contact your Account Team with any additional questions.

Regards,

The MuleSoft Product Team