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.

June 2025

What’s New

Runtime Manager agent:

General improvements:

  • Log4J is upgraded to 2.24.3.

Fixed Issues

Patch release version: 4.9.6

This patch update addresses the following Mule issues:

Issue Resolution ID

Loader constraint violation errors no longer occur when http-connector dependencies exist in both the domain and the policy.

W-17340911

Serialization of result objects with Kryo no longer fails with InaccessibleObjectException in Java 17.

W-17774685

Class loading no longer results in deadlocks caused by a race condition.

W-18388443

A serialization exception no longer occurs when using caching scope.

W-17703164

A classloader leak no longer occurs on undeployment when using lazy service initialization.

W-17750750

The mule.parse.template.use.legacy.default.targetValue compatibility switch is reintroduced to use the legacy default value for the targetValue parameter of the parse-template component. A one-time warning is now logged when enabled.

W-18324755

Serialization now works correctly with API Gateway internal classes.

W-18475283

Preemtive analytics queue deletion is now added.

W-17529530

DataWeave 2.9.4 is bundled with the Mule 4.9.6 release. This patch release addresses the following DataWeave issues:

Issue Resolution ID

XML encoding is now detected before selecting a parser.

W-17637749

The performance of the orderBy function is now improved.

W-18439576

Reading a CSV file inside a MultiPart body now works correctly when performed more than once.

W-17147598

A memory leak of the binding context no longer occurs when using the foreach scope.

W-18472194

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

May 2025

Patch 4.9.5

The May patch update 4.9.5 addresses a regression in the previous May patch update, 4.9.4, and includes the fixes in the patch.

Patch release version: 4.9.5

This patch update addresses the following Mule issues:

Issue Resolution ID

Cluster discovery mechanism now works as expected on Runtime Fabric, CloudHub 2.0, and Anypoint Platform PCE environments, ensuring that schedulers are executed only on the primary node.

W-18528551

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

Patch 4.9.4

What’s New

Runtime Manager agent:

Fixed Issues

Patch release version: 4.9.4

This patch update addresses the following Mule issues:

Issue Resolution ID

Parallel For Each events no longer randomly timeout after a NullPointerException error.

W-17980769

The error message "Couldn’t parse instance of ReentrantReadWriteLock" in ReentrantReadWriteLockSerializer no longer occurs.

W-18057570

Parameters field isn’t serialized in InternalEventImplementation.

W-17703164

Connectivity tests in MTS are now fixed for Java 17.

W-18075077

Exceptions no longer occur when using WebSocket close codes outside a predefined subset. The code now correctly handles all standard/custom WebSocket close codes.

W-17846088

Configuration for preserveHeaderCase is now added in SseSource.

W-18085890

DefaultMessageBuilder no longer contains missing fields.

W-17607446

Contention between transaction and APIkit is now avoided due to tracing initialization.

W-18194349

A schedule is now added to consume the slowly populated pipe to an IO Executor.

W-17444122

org.glassfish:jakarta.json was removed form the distribution.

W-17896357

com.google.code.gson:gson is upgraded to 2.12.1.

W-17896347

com.google.protobuf:protobuf-java is upgraded to v3.25.6.

W-17986761

Custom notifications are now properly dispatched.

W-16091925

DataWeave 2.9.3 is bundled with the Mule 4.9.4 release. This patch release addresses the following DataWeave issues:

Issue Resolution ID

Materialization issues no longer occur when using CSV content inside variables.

W-17167283

DataWeave now preserves trailing zeroes of single-element sum.

W-17283050

A compatibility flag is now added to address the different results produced by calling sizeOf with NumberType.

W-18020856

An unnecessary import is now removed from dw::util::Diff to eliminate a warning when running MUnit.

W-17670504

DataWeave no longer returns a format error on readUnquotedString.

W-18118138

Overflowing no longer occurs while reading large file on multipart format.

W-17644871

Performance issues no longer occur when using Message in DataWeave scripts.

W-18034217

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

April 2025

What’s New

Runtime Manager agent:

Enterprise Edition License:

MuleSoft Government Cloud support coverage:

Fixed Issues

Patch release version: 4.9.3

This patch update addresses the following Mule issues:

Issue Resolution ID

The Netty codec library is now updated to 4.1.119.Final.

W-17980407

You can now use the mule --verifyLicenseDetails [path-to-license.lic] command to verify a given license file.

W-17340620

DuplicateMessageException is now correctly serialized with Kryo.

W-17844603

Error type in raise-error is now correctly resolved when defined with a static property.

W-17339304

org.apache.cxf:cxf-core is now upgraded to version 3.5.10.

W-17896358

Mule runtime no longer fails to start in Windows deployments when the JAVA_HOME environment variable ends with a trailing backslash.

W-18056603

The mule-sdk-api dependency now contains all the required license information.

W-18033237

DataWeave 2.9.2 is bundled with the Mule 4.9.3 release. This patch release addresses the following DataWeave issues:

Issue Resolution ID

Concurrency issues no longer occur when loading modules.

W-17918619

The flat file module no longer fails when loading files with a nested depth greater than 50.

W-17495145

xerces-j is now updated to 2.12.2.

W-16918194

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

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

The com.hazelcast:hazelcast dependency is downgraded to 5.2.5.

W-17905862

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:

Issue Resolution ID

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