Hear from Salesforce leaders on how to create and deploy Agentforce agents.
Register now
Contact Us 1-800-596-4880
  1. Homepage
  2. Release Notes

  3. Mule Runtime Engine 4.9.0 Release Notes

Mule Runtime Engine 4.9.0 Release Notes

Mule runtime engine (Mule) is a lightweight integration engine that runs Mule applications and supports domains and policies.

This version of Mule provides important enhancements and fixes. Deploy all your new and existing applications to the latest version to benefit from the improvements.

March 2025

What’s New

Runtime Manager agent:

Feature Flagging Mechanism:

  • Mule 4.9 incorporates new feature flags. See Feature Flagging Mechanism for a detailed description of each feature flag and configuration instructions.

Fixed Issues

Patch release version: 4.9.2

This patch update addresses the following Mule issues:

Issue Resolution ID

Resources are now properly released after a timeout when using the Scatter-Gather or Parallel For Each routers. The mule.forkJoin.completeChildContextsOnTimeout feature flag is now added to enable this behavior.

W-16941297

MessagingException can now be converted to JSON using DataWeave.

W-16629236

Performance degradation no longer occurs when the nonBlockingWriter is enabled for response streaming.

W-17627284

A race condition introduced by W-17048606 no longer occurs, where the last part of the response body was truncated when streamResponse flag is set to true in request-connection.

W-17617940

grizzly-ahc is now upgraded in HTTP Service.

W-17667949

When using sdk-api version of @Connection and ConnectionProvider in a source, a validation saying that @Connection can only be used with the extensions-api version of ConnectionProvider is no longer triggered.

W-17559243

Kryo serialization issue no longer occurs in Java 17 when running with distributed cluster using authentication, caching policy, and persistent Object Store.

W-16912085

Performance during cache scope execution is now improved.

W-17671126

DataWeave 2.9.1 is bundled with the Mule 4.9.2 release. This patch release addresses the following DataWeave issues:

Issue Resolution ID

The Java reflection lookup strategy is now improved for bean instances.

W-17624594

Consuming values now work as expected when using overloaded materialized functions.

W-17588914

For guidance with the patching process, see Apply Patch Updates.

February 2025

Patch 4.9.1

The February patch update 4.9.1 addresses a regression in the previous February patch update, 4.9.0, and includes the fixes in the patch.

Patch release version: 4.9.1

This patch update addresses the following Mule issues:

Description Issue

ConfigurationException no longer occurs while performing Amazon DynamoDB Connector operations.

W-17801971

For guidance with the patching process, see Apply Patch Updates.

February 6, 2025

What’s New

The 4.9.0 version of Mule runtime introduces the following enhancements:

Java adoption:

  • In Mule 4.9.0 and later, you can compile any Mule project and additional dependencies for Java 17.

  • You can now run applications on Java 17 only.

  • This release supports auto minor upgrades for Java 17 apps between Mule 4.8 Edge and Mule 4.9 Edge, as well as from Mule 4.6 LTS to Mule 4.9 LTS.

  • Java 8 and 11 apps won’t be auto minor upgraded to Mule 4.9, so plan your upgrade path for apps that are running on Java 8 or 11 accordingly.

Feature Flagging Mechanism:

  • Mule 4.9 incorporates new feature flags. See Feature Flagging Mechanism for a detailed description of each feature flag and configuration instructions.

Runtime Manager agent:

General improvements:

  • Mule 4.9 upgrades the subset of libraries from included third-party software. See Third-Party Software in Mule for a detailed description.

DataWeave Features

The 2.9.0 version of DataWeave introduces the following new features and enhancements:

Extended format support:

General improvements:

Fixed Issues

The release addresses the following Mule issues and incorporates all patch updates from the 4.8.0 Mule release through January 2025:

Issue Resolution ID

Spring is upgraded to 6.2.0.

W-16639197

The org.jgrapht:jgrapht-core is upgraded to v1.5.2.

W-16494546

The com.github.ben-manes.caffeine:caffeine is upgraded to v3.

W-16494569

The plexus-component-annotations is upgraded to v2.2.0.

W-16541666

The org.apache.commons:commons-compress is upgraded to v1.27.0.

W-16515101

The com.hazelcast:hazelcast is upgraded to v5.4.0.

W-16594688

The Xerces-J is upgraded to v2.12.2.

W-16980865

The org.jetbrains:annotations is upgraded to v26.

W-16944403

The kotlin is upgraded to v2.

W-16908778

The org.togglz:togglz-core is upgraded to v4.

W-16881509

The graal-sdk is upgraded to v24.1.1.

W-16772392

The byteBuddy is upgraded to v1.15.1.

W-16778624

The org.apache.xmlbeans:xmlbeans is upgraded to v5.

W-15263392

The com.lmax:disruptor is upgraded to v4.

W-16514909

Compile target is now set to Java 17.

W-16045353

An error message now indicates if a classloader fails to be created for a service.

W-17244755

DataWeave 2.9.0 is bundled with the Mule 4.9.0 release. This release addresses the following DataWeave issues:

Issue Resolution ID

Java module now honors Java bean accessor methods.

W-17142345

Bundled Components

  • DataWeave version 2.9.0

  • Runtime Manager Agent plugin version 2.6.7

Upgrade

If you are upgrading to this version of Mule from an earlier Mule 4.x version, see Mule Upgrades and Patch Updates.

To ensure optimal performance with this version of Mule and avoid unexpected issues, update the following modules and extensions to their latest version at the time of this release:

Module or Extension Version

APIkit for Mule 4

1.11.3

APIkit for OData

2.3.0

APIkit for OData 4

1.5.2

APIkit for SOAP

1.6.0

APIkit for GraphQL

1.1.0

Spring module

1.4

MUnit plugin

3.4.0

Considerations for Mule Extension Developers

If you update the version of your parent pom.xml file to 1.4.0 or later when you build a Mule extension, ensure that the dependencies in your pom.xml file do not override dependencies defined in the parent pom.xml file, and declare only the dependencies you need. If you need to declare a dependency that is already declared in the parent pom.xml file, do not specify a version so it uses the version from the parent pom.xml file.

See Also