Mule Runtime Engine 4.10.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.

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

October 2, 2025

What’s New

The 4.10.0 version of Mule runtime introduces these enhancements:

Mule Troubleshooting Plugin:

Mule 4.10 introduces the Mule Troubleshooting plugin, which generates a structured diagnostic archive (DIAF) to simplify troubleshooting, consolidate runtime metrics, and provide consistent data for MuleSoft Support. It works across all deployment models and helps investigate performance issues, application errors, and scheduler activity. See Mule Troubleshooting Plugin for more information.

Feature Flagging Mechanism:

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

Runtime Manager agent:

This release of Mule runtime 4.10.0 includes Runtime Manager agent 2.7.7. See Runtime Manager Agent 2.7.7 Release Notes.

Updated TLS Configuration Behavior:

To enhance security, TLS configuration now loads trust store and key store files as classloader resources by default. For on-premises deployments (hybrid or standalone) that require access to certificates from the file system, set the mule.tlsStores.filesystemLookup.enable system property to true.

Connector updates:

HTTP Connector: You can now enable the HTTP/2 feature in the HTTP Connector for faster, more secure, and more efficient communication in your Mule apps. See HTTP/2 Support.

General improvements:

Mule 4.10 upgrades the subset of libraries from included third-party software. See Third-Party Software in Mule for a detailed description.
The org.quartz-scheduler:quartz library is upgraded to 2.5.0.
The org.vibur:vibur-object-pool library is upgraded to 26.
The commons-beanutils:commons-beanutils library is upgraded to 1.10.0.
The jakarta-annotation library is upgraded to 2.1.1.
The mockito monorepo is upgraded to 5.
The log4j2 monorepo is upgraded to 2.25.1.
The netty library is upgraded to 4.1.127.Final.
The spring library is upgraded to 6.2.10.
The rhino library is upgraded to 1.8.0.
The com.github.ben-manes.caffeine:caffeine library is upgraded to 3.2.2.
The io.opentelemetry:opentelemetry-bom library is upgraded to 1.49.0.
The jcommander library is upgraded to 2.0.

DataWeave Features

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

DataWeave Logging Configuration:

You can now configure DataWeave logging to control log levels and improve debugging and monitoring. See DataWeave Logging Configuration for details.

DataWeave module features:

The logDebug function (logDebug) is new.
The logError function (logError) is new.
The logInfo function (logInfo) is new.
The logWarn function (logWarn) is new.
The logWith function (logWith) is new.
The decimalAdd function (decimalAdd) is new.
The decimalDivide function (decimalDivide) is new.
The decimalMultiply function (decimalMultiply) is new.
The decimalPow function (decimalPow) is new.
The decimalRound function (decimalRound) is new.
The decimalSqrt function (decimalSqrt) is new.
The decimalSubtract function (decimalSubtract) is new.
The Math Types (Math Types) are new.

General improvements:

DataWeave incorporates new system properties. See DataWeave System Properties.
DataWeave now supports Avro primitive types as top-level schema elements. See Avro Format.

Fixed Issues

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

Issue Resolution ID

Issue Resolution	ID
The org.quartz-scheduler:quartz library is upgraded to 2.5.0.	W-17406808
The org.vibur:vibur-object-pool library is upgraded to 26.	W-17570586
The commons-beanutils:commons-beanutils library is upgraded to 1.10.0.	W-17571116
The jakarta-annotation library is upgraded to 2.1.1.	W-17927646
The Mockito monorepo is upgraded to 5.	W-18685961
The Log4j2 monorepo is upgraded to 2.25.1.	W-18834079
The Netty library is upgraded to 4.1.127.Final.	W-19559645
The Rhino library is upgraded to 1.8.0.	W-17636627
The org.springframework : spring-core library is upgraded to 6.2.10.	W-19353311
The org.apache.cxf:cxf-core library is now upgraded to 3.5.11.	W-17264514
Memory leaks no longer occur when a reconnection is configured in a Mule domain and referenced from multiple applications.	W-17857080
`InaccessibleObjectException` errors no longer occur when using cluster mode on Java 17.	W-18667744
Fork-join routers no longer create unnecessary schedules when the timeout is set to infinite.	W-18347293
Potential deadlocks during deployment no longer occur when using some custom Log4j appenders.	W-19675881
Cookies now propagate correctly across multiple redirect scenarios.	W-18971065
The Netty library is upgraded to 4.1.124.Final.	W-19341592
The `org.mule.runtime.api.serialization.SerializationException: Could not deserialize object` errors no longer occur when processing the payload of a Query XML stream using transfer message in a Choice Router.	W-18902280
SSE clients now parse events that don’t include an `event` field. They default to `message` as described in the spec.	W-19667148
Possible starvation no longer occurs when sending HTTP responses that are generated slowly.	W-19471841
Gatekeeper deadlock errors no longer occur during race conditions among contract downloads and policy application.	W-19407164

The org.quartz-scheduler:quartz library is upgraded to 2.5.0.

W-17406808

The org.vibur:vibur-object-pool library is upgraded to 26.

W-17570586

The commons-beanutils:commons-beanutils library is upgraded to 1.10.0.

W-17571116

The jakarta-annotation library is upgraded to 2.1.1.

W-17927646

The Mockito monorepo is upgraded to 5.

W-18685961

The Log4j2 monorepo is upgraded to 2.25.1.

W-18834079

The Netty library is upgraded to 4.1.127.Final.

W-19559645

The Rhino library is upgraded to 1.8.0.

W-17636627

The org.springframework : spring-core library is upgraded to 6.2.10.

W-19353311

The org.apache.cxf:cxf-core library is now upgraded to 3.5.11.

W-17264514

Memory leaks no longer occur when a reconnection is configured in a Mule domain and referenced from multiple applications.

W-17857080

InaccessibleObjectException errors no longer occur when using cluster mode on Java 17.

W-18667744

Fork-join routers no longer create unnecessary schedules when the timeout is set to infinite.

W-18347293

Potential deadlocks during deployment no longer occur when using some custom Log4j appenders.

W-19675881

Cookies now propagate correctly across multiple redirect scenarios.

W-18971065

The Netty library is upgraded to 4.1.124.Final.

W-19341592

The org.mule.runtime.api.serialization.SerializationException: Could not deserialize object errors no longer occur when processing the payload of a Query XML stream using transfer message in a Choice Router.

W-18902280

SSE clients now parse events that don’t include an event field. They default to message as described in the spec.

W-19667148

Possible starvation no longer occurs when sending HTTP responses that are generated slowly.

W-19471841

Gatekeeper deadlock errors no longer occur during race conditions among contract downloads and policy application.

W-19407164

DataWeave 2.10.0 is bundled with the Mule 4.10.0 release. This release addresses the following DataWeave issues:

Issue Resolution ID

Issue Resolution	ID
The `take` function now works with streaming when argument is larger than the array length.	W-19168279
`java-module` now supports object fields access when using different capitalizations.	W-19477334

The take function now works with streaming when argument is larger than the array length.

W-19168279

java-module now supports object fields access when using different capitalizations.

W-19477334

Bundled Components

DataWeave version 2.10.0
Runtime Manager Agent plugin version 2.7.7

Upgrade

If you’re 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

When you build a Mule extension, if you update the version of your parent pom.xml file to 1.4.0 or later, ensure that the dependencies in your pom.xml file don’t override dependencies in the parent pom.xml file. Declare only the dependencies you need. If you declare a dependency that’s already in the parent pom.xml file, don’t specify a version, so that it uses the version from the parent pom.xml file.