Contact Us 1-800-596-4880
  1. Homepage
  2. Release Notes

  3. Mule Runtime Engine 4.10.0 Release Notes

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.

November 2025

What’s New

Runtime Manager agent:

General improvements:

Fixed Issues

Patch release version: 4.10.1

This patch update addresses these Mule issues:

Issue Resolution ID

OpenTelemetry current API sampling decisions now propagate correctly through http:requester calls to downstream APIs.

W-19784910

UndeclaredThrowableException errors no longer occur during Bitronix reconnection.

W-15196888

InaccessibleObjectException errors no longer occur during deployment when the mule.classloading.verbose property is set.

W-18563387

MDC information is now properly preserved when using loggers inside custom Java code invoked from a DataWeave script.

W-18912999

Batch queuestore files now clean up correctly in rare load failure scenarios such as out-of-memory errors.

W-17935223

Builds no longer fail when running tests from an extension that uses Mule SDK with Java 8 through Java 17.

W-18964335

The until-successful scope now honors the graceful shutdown timeout. To enable this behavior, set these system properties: mule.untilSuccessful.retryOnCriticalError.disallow=true and mule.forcefulShutdown.raiseCancelledError=true.

W-19648397

Hashing now uses toHex conversion to prevent “null character” or other invalid characters from being used as IDs in the redelivery policy. This change is feature-flagged. To enable it in version 4.10, set the mule.redeliveryPolicy.encode.secureHash system property to true.

W-18584560

IllegalAccessException errors no longer occur when DataWeave serializes error.errorMessage in a Scatter-Gather error route.

W-19340663

Mule applications that use TLS KeyStore configurations no longer fail to deploy with “NO MODEL RESOLVED” warnings and ConfigurationException errors.

W-16565012

Mule Troubleshooting Plugin executions no longer fail when the IP address changes.

W-19802474

The reactor.netty library is upgraded to 1.2.10.

W-17264514

The netty library is upgraded to 4.1.127.Final.

W-19995637

The spring-core library is upgraded to 6.2.11.

W-19674953

The Bump handlebars library is upgraded to 4.4.0.

W-1906465

The HTTP listener now correctly populates attributes.queryParams when using HTTP/2.

W-19802358

close_notify events sent by a server are now properly handled by the HTTP/2 client.

W-19973575

DataWeave 2.10.1 is bundled with the Mule 4.10.1 release. This patch release addresses these DataWeave issues:

Issue Resolution ID

Materialization errors no longer occur in run function.

W-19884071

The org.apache.commons:commons-lang3 library is upgraded to 3.18.

W-19803454

Single variable materialization now works correctly for unsafe and exists selectors.

W-19581017

The SnakeYAML library is upgraded.

W-19749213

Each variable is now extracted from vars to manage materialization individually.

W-19580992

The -- operator now returns the correct type without the subtracted keys.

W-19595907

Debug logging is now enabled for DefaultLoggingService.

W-19650046

The take function no longer fails in streaming mode when n is larger than the array length.

W-19168279

The Java Module now supports object field access with different capitalizations.

W-19477334

The Runtime Compiler now uses the Parser Manager to look for resources provided as parameters.

W-19376888

A null check is now performed before closing the InputStream.

W-19395982

Parsing metrics printing now includes a missing line ending.

W-19440583

Constants are now used to prevent incorrect loader identifiers for binary compiled scripts.

W-18455133

Generated POM files now include license information.

W-19439330

SchemaProvider resolution on Types is improved to prevent Execution reference leaks.

W-19389019

The classloader weave resource resolver now uses the correct path in Windows environments.

W-19407283

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:

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:

DataWeave module features:

General improvements:

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

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

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.

See Also