--- schema_version: "1" id: a67a58de9bd006a3d12520132867f8afbfedf28a336452e6bec591874aec2a64 title: Mule Runtime Engine 4.11.0 Release Notes collection: mulesoft version: current locale: ja-jp portal_url: https://docs.salesforce.com/mulesoft/current/ja-jp/release-notes/mule-runtime/mule-4.11.0-release-notes.md canonical_url: https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.11.0-release-notes source_site: docs.mulesoft.com content_type: documentation content_hash: 94afc928076688f378c454a7b1ddf7bfc971d642273bdfa4bd0fe77d87d80b66 description: MuleSoft Documentation Site latest: true --- # Mule Runtime Engine 4.11.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](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#july-2026)July 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.11.6 includes Runtime Manager agent 2.7.16. See [Runtime Manager Agent 2.7.16 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-16). Feature Flagging Mechanism: - Mule 4.11 incorporates new feature flags. See [Feature Flagging Mechanism](https://docs.mulesoft.com/mule-runtime/latest/feature-flagging) for a detailed description of each feature flag and configuration instructions. General improvements: - The Mule Troubleshooting plugin now includes additional diagnostic sections in the Diagnostic Information Analysis File (DIAF). See [Mule Troubleshooting Plugin](https://docs.mulesoft.com/mule-runtime/latest/mule-troubleshooting-plugin) for more information. - System Info: Reports host-level diagnostics including OS details, CPU metrics, memory, and disk input and output statistics. - JVM Agents: Lists agents attached at JVM startup via `-javaagent`, `-agentpath`, or `-agentlib` arguments. - Connectors State: Shows connector configuration states, connection pools, errors, and TLS details. - Cluster Info: Reports clustering configuration and distributed lock diagnostics. ### Fixed Issues Patch release version: 4.11.6 This patch update addresses these Mule issues:
Issue Resolution ID

Cluster node IDs are no longer generated with negative values.

W-22294724

Graceful shutdown no longer times out when a global error handler runs for a flow.

W-22434375

Long-running internal tasks no longer use the shared forkJoin pool during parallel flow shutdown and bootstrap configuration, preventing thread starvation.

W-22279521

Duplicate XSD elements are no longer generated for connection providers declared at both the extension and configuration levels.

W-20824537

Shutdown validation for dynamic configurations can now be skipped by enabling the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property.

W-22772644

Flows with a scheduler source are no longer left in an invalid state after a flow restart.

W-22918240

Stopping a flow no longer waits unnecessarily when no events are being processed.

W-22969411

Project versions defined with properties are now resolved recursively.

W-22845430

Extension packager validation no longer fails for operations annotated with @Validator that use a CompletionCallback operation.

W-22817376

Events that are dropped within a processing hook are now properly completed and terminated.

W-22470584

The Netty HTTP listener now rejects HTTP/1.1 requests that have a missing or duplicate host header, in compliance with RFC 9112.

W-23052713

The maximum size of the dynamic flow-ref cache is now configurable through the mule.flowRef.dynamicCacheMaxSize system property, which defaults to 20.

W-22219018

API Gateway contract persistence can now be disabled by setting the anypoint.platform.contracts_persistence_enabled system property to false, avoiding errors when persisting large numbers of contracts.

W-22568982

The c3p0 library is upgraded to 0.14.1.

W-22990152

The Spring Framework is upgraded to 6.2.19.

W-3300013

The Bitronix Transaction Manager library is upgraded to 3.0.2.

W-22405007

The OpenTelemetry API library is upgraded to 1.62.0.

W-22806044

The Netty library is upgraded to 4.2.15.Final.

W-22888966

The Reactor Netty library is upgraded to 1.3.6.

W-22939412
DataWeave 2.11.5 is bundled with the Mule 4.11.6 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

Scope resolution errors no longer occur when importing Java classes with self-referential array properties.

W-22914494

AvroReader no longer causes memory leaks when processing Avro data in long-running flows.

W-22364385
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#june-2026)June 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.11.5 includes Runtime Manager agent 2.7.15. See [Runtime Manager Agent 2.7.15 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-15). ### Fixed Issues Patch release version: 4.11.5 This patch update addresses these Mule issues:
Issue Resolution ID

Connectivity testing of configurations in clustered deployments no longer uses distributed locks, preventing deadlocks.

W-22248198

Fatal errors such as StackOverflowError are now logged instead of being consumed by internal error handling.

W-22496803

Mule no longer hangs during shutdown when a parameter validation exception occurs during flow execution.

W-22248534

Race conditions in outerFluxCompletionScheduler no longer occur during graceful shutdown.

W-22343018

The ObjectStore retrieved from the Registry in OAuthHandler is now properly initialized and started.

W-22373641

SDK parameter validation errors now raise the MULE:VALIDATION error type instead of MULE:UNKNOWN.

W-22276522

Race conditions during policy redeployment that caused Mule to stop processing events permanently no longer occur.

W-22343705

ConcurrentModificationException errors no longer occur when multiple plugins with shared dependencies are deployed simultaneously.

W-21193046

Cluster encryption now uses the configured algorithm correctly instead of defaulting to Blowfish.

W-21666905

The error type in the EE Cache scope is now correctly reported as MULE:RETRY_EXHAUSTED instead of EE:RETRY_EXHAUSTED when until-successful exhausts its retries.

W-21525972

Large Anypoint Platform authentication failure responses no longer cause excessive log bloat.

W-21882516

HTTP Server now supports Upgrade requests to h2c even when the request contains a non-empty body.

W-22506085

Test Connection for The HTTP listener now correctly reports a failure when an unresolvable hostname is configured in the Host field.

W-21921687

The Spring Core library is upgraded to 6.2.18.

W-22169898

Persistent ObjectStore or Batch data serialized before a patch upgrade now deserializes correctly after upgrading.

W-22623626

OutOfMemory errors no longer occur when establishing SSL connections with HTTP endpoints.

W-22547971
DataWeave 2.11.4 is bundled with the Mule 4.11.5 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

StackOverflowError errors no longer occur when computing or converting type metadata for self-referencing recursive types.

W-21712344

The Java bean metadata cache no longer performs unnecessary evictions when processing Java POJOs. A new per-app Java bean cache can be enabled with the per_app_java_bean_cache compatibility flag.

W-22417507

The Java module bean introspection cache no longer causes memory leaks.

W-22419118
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#may-2026)May 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.11.4 includes Runtime Manager agent 2.7.13. See [Runtime Manager Agent 2.7.13 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-13). FIPS 140-3 Compliance Support: - You can now configure Mule runtime to operate in a FIPS 140-3-compliant environment using certified cryptography providers. See [FIPS 140-3 Compliance Support](https://docs.mulesoft.com/mule-runtime/latest/fips-140-3-compliance-support) for more information. General improvements: - The `diaf` Event Dump now includes two additional `eventContextState` values: `PENDING` and `WAITING_NON_BLOCKING`. See [Mule Troubleshooting Plugin](https://docs.mulesoft.com/mule-runtime/latest/mule-troubleshooting-plugin) for more information. ### Fixed Issues Patch release version: 4.11.4 This patch update addresses these Mule issues:
Issue Resolution ID

Configuration references to configs defined in a parent domain are now properly validated at deployment time, preventing unclear runtime errors.

W-11453332

Extension operations using @Content parameters with complex map structures no longer fail to deploy.

W-18034452

The Grizzly HTTP library is upgraded to 2.3.36-MULE-029.

W-21337433

Netty HTTP client NTLM authentication no longer fails due to missing TCP connection affinity during the handshake.

W-21615520

The plexus-utils library is upgraded to 4.0.3.

W-21774430

The HTTP listener now gracefully handles non-RFC-compliant date formats in Set-Cookie Expires attributes.

W-21860840

The Netty library is upgraded to 4.2.12.Final.

W-21913252

HTTP 304 (Not Modified) responses sent through the HTTP listener no longer include an incorrect Content-Length header.

W-21632770

Netty HTTP client no longer sends an incorrect WWW-Authenticate header during the NTLM authentication handshake.

W-21762949

In-memory Object Store partitions now correctly use cluster-wide storage when deployed to a cluster with the Object Store plugin enabled.

W-17714668

A memory leak in dynamic flow-ref resolution that could eventually lead to an OutOfMemoryError no longer occurs.

W-22013292

Deserialization errors no longer occur in Redis-backed Object Stores when accessing cached data created on an earlier Mule runtime version.

W-20880559

A serialization error that could occur when deserializing data after a Mule runtime upgrade no longer occurs.

W-21951097

API Gateway contracts for public OAuth clients using PKCE are no longer dropped when the client secret is null.

W-21177224

The support-tools-installer is removed from the Mule runtime distribution.

W-21842339
DataWeave 2.11.3 is bundled with the Mule 4.11.4 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

atBeginningOfDay now returns the midnight offset on DST days, instead of the input offset.

W-21614817
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#april-2026)April 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.11.2 includes Runtime Manager agent 2.7.11. See [Runtime Manager Agent 2.7.11 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-11). Feature Flagging Mechanism: - Mule 4.11 incorporates new feature flags. See [Feature Flagging Mechanism](https://docs.mulesoft.com/mule-runtime/latest/feature-flagging) for a detailed description of each feature flag and configuration instructions. ### Fixed Issues Patch release version: 4.11.3 This patch update addresses these Mule issues:
Issue Resolution ID

The c3p0 library is upgraded to 0.12.0.

W-21391116

The mchange-commons-java library is upgraded to 0.4.0.

W-21391115

NullPointerException errors no longer occur in the Log4j boot configuration during application shutdown when shutdown callbacks are canceled while the Log4j context factory is disposing, which previously caused failures due to concurrent execution of dispose() and cancel().

W-20256082

Until Successful scopes no longer continue retrying during application shutdown when using flow-ref.

W-20267296

NullPointerException: No Context at location errors no longer occur when using operation policies with routers or scopes.

W-20791354

OAuth token storage now correctly uses custom ObjectStores (such as Redis) configured through the Object Store parameter when they’re registered in the application registry instead of the ObjectStoreManager.

W-19811593

Exception reached subscriber errors no longer occur when combining interceptors and operation policies.

W-21250126

Scheduler jobs no longer deadlock during flow shutdown.

W-21263748

TLS Context can now be initialized during application deployment by using the mule.enable.inline.tls.context.initialization feature flag.

W-20038933

OpenTelemetry Direct streaming now supports FIPS-compatible keystore format.

W-20623905

A warning now appears when an OpenTelemetry property is incorrectly used as a deployment property.

W-21018072

NullPointerException errors no longer occur in message processor chain alerting when reporting dropped errors or events if alerting support isn’t found for the current classloader. When alerting support isn’t available, the hooks now skip the alert and log the condition instead of invoking it on a null reference.

W-20192960

Netty no longer attempts to send more bytes than specified in the Content-Length header.

W-21184863

Netty server read timeouts now consider requests being read instead of requests being processed.

W-21321115

Netty HTTP Client no longer throws exceptions when a proxy server returns a 407 response and now returns the 407 response instead.

W-21465366

Netty response timeout behavior is now consistent with Grizzly.

W-21547186

Netty TLS connection failures now appear as DEBUG logs instead of WARN logs.

W-21428392

Netty HTTP Client now filters duplicate Content-Type headers.

W-21344116

The exception raised by Netty for unresolved addresses is now consistent with the Grizzly implementation.

W-21515340

HTTP Netty implementation performance is now improved.

W-20969515

HTTP Server no longer logs an error when a client closes an idle keep-alive connection.

W-21431822
DataWeave 2.11.2 is bundled with the Mule 4.11.3 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

The Avro library is upgraded to 1.12.1. The Jackson Core library is upgraded to 2.21.1.

W-21415439

The Jakarta Mail library is upgraded to 2.1.5.

W-21320250

The range operator now returns null for invalid ranges.

W-21781423
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#march-2026)March 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.11.2 includes Runtime Manager agent 2.7.10. See [Runtime Manager Agent 2.7.10 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-10). Feature Flagging Mechanism: - Mule 4.11 incorporates new feature flags. See [Feature Flagging Mechanism](https://docs.mulesoft.com/mule-runtime/latest/feature-flagging) for a detailed description of each feature flag and configuration instructions. ### Fixed Issues Patch release version: 4.11.2 This patch update addresses these Mule issues:
Issue Resolution ID

When the mule.forcefulShutdown.dynamicConfig.disableStoppingCheck system property is enabled, the dynamic configuration check is disabled during graceful shutdown.

W-20890587

When the mule.forcefulShutdown.raiseCancelledError feature flag is enabled, Mule runtime now raises a MULE:CANCELLED error instead of a MULE:UNKNOWN error if it attempts to create a dynamic configuration during shutdown.

W-20890613

Extensions no longer export mule-sdk-api and jakarta dependencies in the mule-artifact.json file.

W-21001749

Client certificates (optional) are no longer requested when no trust store is configured.

W-21220031

Public flows now stop concurrently during graceful shutdown.

W-21228085

Deadlocks no longer occur during log reconfiguration when policies are applied.

W-21231834

When the mule.enableLogEventDumpOnShutdown system property is enabled, the event dump is now logged during application shutdown.

W-21232374

XSD validations are now enabled by default during deployment.

W-21139633

Errors that are not MessagingException errors are no longer silenced.

W-21043969

The reactor.netty.version library is upgraded to 1.3.2.

W-3300013

When the mule.propagate.objectStore.customization.to.policies feature flag is enabled, policies now respect their configured TTL when using Object Store v2.

W-21215761

The "java.lang.IllegalStateException: The client must be started before use." error no longer occurs when requesting an OAuth access token.

W-17689958

The "API is blocked (unavailable)" log message no longer appears during policy updates without a corresponding unblocked message.

W-20633888

APIkit flows that use non-default names and are mapped through the flow-mapping parameter on apikit:config are now correctly counted as public flows instead of being treated as private.

W-18668900
DataWeave 2.11.1 is bundled with the Mule 4.11.2 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

The Array range selector operator no longer experiences performance degradation.

W-20220578

Concurrent access to KeyValuePairs inside lazy materialized objects no longer causes unexpected behavior.

W-21045501

The Mapping Editor API now supports attributes in Anypoint Code Builder.

W-20662336

Updating the expression model in the Mapping Editor API now works correctly.

W-20611263
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#february-2026)February 2026 ### [](#patch-4-11-1)Patch 4.11.1 - This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990. ## [](#february-4-2026)February 4, 2026 ### [](#patch-4-11-0)Patch 4.11.0 ### What’s New The 4.11.0 version of Mule runtime introduces these enhancements: Batch Errors Handling: - Mule 4.11 introduces a new way to handle batch errors. Batch processing now captures record-level failures as `BatchError` objects that provide structured access to error details through DataWeave. To access `BatchError` fields, your application must use `minMuleVersion` 4.10 or later, or you must set the `com.mulesoft.dw.java.enabled_class_definition_lookup=true` system property. See [Batch Errors](https://docs.mulesoft.com/mule-runtime/latest/batch-error-concept) for more information. OpenTelemetry Direct Telemetry Stream: - You can now export OpenTelemetry traces and logs directly from Mule runtime to a customer-managed OpenTelemetry collector by using the Direct Telemetry Stream. This feature enables standards-based observability outside Anypoint Monitoring, supports log and trace correlation, configurable sampling and backpressure strategies, and secure transmission with mTLS. See [OpenTelemetry Support in Mule Runtime](https://docs.mulesoft.com/mule-runtime/latest/otel-support) for more information. Feature Flagging Mechanism: - Mule 4.11 incorporates new feature flags. See [Feature Flagging Mechanism](https://docs.mulesoft.com/mule-runtime/latest/feature-flagging) for a detailed description of each feature flag and configuration instructions. Runtime Manager agent: - This release of Mule runtime 4.11.0 includes Runtime Manager agent 2.7.9. See [Runtime Manager Agent 2.7.9 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-9). General improvements: - Mule 4.11 upgrades the subset of libraries from included third-party software. See [Third-Party Software in Mule](https://docs.mulesoft.com/mule-runtime/latest/third-party-software-in-mule) for a detailed description. - You can now view the OpenTelemetry export queue full alert in the `diaf` file. See [Mule Troubleshooting Plugin](https://docs.mulesoft.com/mule-runtime/latest/mule-troubleshooting-plugin) for more information. - Mule runtime now uses NETTY as the default HTTP service implementation. To use the legacy GRIZZLY implementation, set the `mule.http.service.implementation` system property to `GRIZZLY`. See [Before you begin (HTTP/2 Support)](https://docs.mulesoft.com/http-connector/latest/http-2-support#before-you-begin) for requirements and configuration details for enabling HTTP/2 with NETTY. ## [](#dataweave-features)DataWeave Features The 2.11.0 version of DataWeave introduces these new features and enhancements: Streaming and Memory Efficiency: - The [dw::core::Binaries::fromBase64](https://docs.mulesoft.com/dataweave/latest/dw-binaries-functions-frombase64) and [dw::core::Binaries::toBase64](https://docs.mulesoft.com/dataweave/latest/dw-binaries-functions-tobase64) functions now process input data in chunks instead of loading the entire String or Binary into memory. This improves scalability and helps prevent out-of-memory errors when working with large payloads. Lazy Variable Materialization: - [Variables](https://docs.mulesoft.com/dataweave/latest/dataweave-variables) are now materialized independently and only when needed. This reduces unnecessary memory usage and improves performance, especially in complex transformations with multiple variables. Enhanced try Function Behavior: - The [try](https://docs.mulesoft.com/dataweave/latest/dw-runtime-functions-try) function now performs eager materialization of its execution scope. This ensures that all expressions inside the try block are executed and that any errors are properly caught during execution. General improvements: - DataWeave libraries are now precompiled during service startup, reducing warm-up time and improving first-execution performance. - Memory usage during DataWeave parsing and compilation is now optimized, resulting in a smaller overall memory footprint for applications using DataWeave. - DataWeave incorporates new system properties. See [DataWeave System Properties](https://docs.mulesoft.com/dataweave/latest/dataweave-system-properties). ### Fixed Issues The release addresses these Mule issues and incorporates all patch updates from the 4.10.0 Mule release through January 2026:
Issue Resolution ID

HTTP/2 connections now correctly multiplex when processing concurrent requests, reducing connection creation and latency.

W-19860076

The runtime now leverages the AST file for applications with the until-successful component instead of parsing configuration XML files.

W-20283146

Batch record deserialization no longer fails when a Netty exception occurs.

W-20552358

Inbound HTTP/2 header validation is now improved.

W-19873453

The org.apache.logging.log4j:log4j-core dependency is upgraded to 2.25.3.

W-20679050
DataWeave 2.11.0 is bundled with the Mule 4.11.0 release. This release addresses these DataWeave issues:
Issue Resolution ID

AST scope navigation now works correctly for cross-file references when using the Tooling API.

W-20212809

A specific overload for isEmpty on binaries is now available to prevent implicit coercion to other types.

W-20049958

Materialized Java values are now cached to allow multiple executions using the same value.

W-20091279

Semantic tokens are now supported in the Tooling API.

W-19846990

NullPointerException no longer occurs when handling annotation types.

W-19853000

LogLevel documentation is now included directly in the code.

W-17800393

The commons-beanutils library is upgraded.

W-3300013

Base64 encoding and decoding now support payloads larger than memory.

W-18575719

Eager materialization is now supported on values, enabling caching of all exceptions inside the try function.

W-19717874

Avro enum, map, union, and fixed types are now supported as top-level elements.

W-19596039

WeaveCompiler now allows precompiling mappings and modules without validation or type checking.

W-19667273

Type check errors are now correctly reported when resolving type checking on subgraphs.

W-19564697

Lazy loading of source files is now enabled during binary compilation, avoiding unnecessary memory usage.

W-19594703

Type inference now works correctly when using the -- operator to subtract a key from an object.

W-19595907

Warning and error messages now propagate correctly between compilation phases.

W-19386849

Base types are now used to validate accepted values, preventing premature materialization.

W-18943395

Optional types now propagate correctly through chains of value selectors.

W-19272070

The syntax version is now added to TypeGraph and WeaveTypeResolution.

W-19271992

The classloader resource resolver now resolves paths correctly on Windows systems.

W-19407283
## [](#bundled-components)Bundled Components - DataWeave version 2.11.0 - Runtime Manager Agent plugin version 2.7.9 ### Upgrade If you’re upgrading to this version of Mule from an earlier Mule 4.x version, see [Mule Upgrades and Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-esb#mule-upgrades). To ensure optimal performance with this version of Mule and avoid unexpected issues, update these modules and extensions to their latest version at the time of this release:
Module or Extension Version

APIkit for Mule 4

1.11.10

APIkit for OData

2.3.4

APIkit for OData 4

1.5.4

APIkit for SOAP

1.6.7

APIkit for GraphQL

1.1.1

Spring module

2.1.1

MUnit plugin

3.6.3
## [](#considerations-for-mule-extension-developers)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)See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) - [Mule Troubleshooting Plugin](https://docs.mulesoft.com/mule-runtime/4.11/mule-troubleshooting-plugin) - [Known Issues](https://help.salesforce.com/s/issues)