---
schema_version: "1"
id: 3352ea38a780eb84e494b2f41b95d8a5756835d5a01cff9a04db473196fdf40c
title: Mule Runtime Engine 4.6.0 Release Notes
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/release-notes/mule-runtime/mule-4.6.0-release-notes.md
canonical_url: https://docs.mulesoft.com/release-notes/mule-runtime/mule-4.6.0-release-notes
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 5e13ee97770547bc510503360c160e90c2ee6289fd2bcea018074df3dc01fb63
description: MuleSoft Documentation Site
latest: true
---
---
product: Release Notes
version: master
---

# Mule Runtime Engine 4.6.0 Release Notes

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

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.

## October 2026

### Fixed Issues

### Patch 4.6.36

The October patch update 4.6.36 addresses regressions in the October patch update 4.6.35.

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><th colspan="2"><p>Mule</p></th></tr><tr><td><div><div><p>SLA-based rate limiting policies no longer reject valid client requests because the client is validated twice.</p></div></div></td><td><div><div><p>W-24447995</p></div></div></td></tr></tbody></table>

### Patch 4.6.35

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.35 includes Runtime Manager agent 2.7.20. See
  [Runtime Manager Agent 2.7.20 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-20).

### Fixed Issues

Patch release version: 4.6.35

This patch update addresses these Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The Reactor Core library is upgraded to 3.8.7.</p></div></div></td><td><div><div><p>W-3300013</p></div></div></td></tr><tr><td><div><div><p>The Jackson library is upgraded to 2.22.2.</p></div></div></td><td><div><div><p>W-23947149</p></div></div></td></tr><tr><td><div><div><p>The jsoup library is upgraded to 1.23.2.</p></div></div></td><td><div><div><p>W-23987949</p></div></div></td></tr><tr><td><div><div><p>Configuration property placeholder resolution now stops once it exceeds a maximum nesting depth, instead of continuing to recurse through a cyclic or excessively deep reference chain. You can configure the depth limit through the <code>mule.properties.resolution.maxDepth</code> system property, which defaults to 10.</p></div></div></td><td><div><div><p>W-23650198</p></div></div></td></tr><tr><td><div><div><p>Error-mapping preservation during error propagation can now be enabled through the <code>mule.honourErrorMappingsOnErrorPropagation</code> system property. When enabled, an error whose type was already resolved inside a scope, including any remapping by an error mapping, keeps that resolved type as it propagates out of the scope, instead of reverting to the raw connector error type.</p></div></div></td><td><div><div><p>W-23955755</p></div></div></td></tr><tr><td><div><div><p>A connector’s message source no longer deadlocks when its connection-retry logic triggers a stop of the retry scheduler from one of that scheduler’s own worker threads.</p></div></div></td><td><div><div><p>W-24234538</p></div></div></td></tr><tr><td><div><div><p>Network information listening ports are now scoped to the Mule process.</p></div></div></td><td><div><div><p>W-24043880</p></div></div></td></tr><tr><td><div><div><p><code>NullPointerException</code> errors no longer occur when loading the extension model of a connector whose connection provider uses the <code>@ClientCredentials</code> or <code>@AuthorizationCode</code> OAuth annotation with <code>credentialsPlacement</code> configured.</p></div></div></td><td><div><div><p>W-24086656</p></div></div></td></tr><tr><td><div><div><p>Policy logging context is no longer lost when a dynamic Flow Reference resolves to a subflow.</p></div></div></td><td><div><div><p>W-24026465</p></div></div></td></tr><tr><td><div><div><p>The new <code>loggingConfiguration</code> troubleshooting operation helps you diagnose logging configuration issues.</p></div></div></td><td><div><div><p>W-23998256</p></div></div></td></tr><tr><td><div><div><p>The log level for <code>disallowConcurrentExecution</code> messages is changed from WARN to DEBUG, reducing log noise.</p></div></div></td><td><div><div><p>W-24164028</p></div></div></td></tr><tr><td><div><div><p>The new on-demand connectivity-testing troubleshooting operation is now available.</p></div></div></td><td><div><div><p>W-23629284</p></div></div></td></tr><tr><td><div><div><p>An SDK API for queues (VM usage) and core adapters is added.</p></div></div></td><td><div><div><p>W-19439432</p></div></div></td></tr><tr><td><div><div><p>The new on-demand <code>connectionCount</code> troubleshooting operation is now available.</p></div></div></td><td><div><div><p>W-23716301</p></div></div></td></tr><tr><td><div><div><p>A warning is now logged when NTLM authentication is configured but the server doesn’t issue an NTLM challenge.</p></div></div></td><td><div><div><p>W-17651806</p></div></div></td></tr><tr><td><div><div><p>Fallback is now enabled as the default strategy for contracts collection. To change the behavior, configure the <code>anypoint.platform.clients_fetch_mode</code> system property with the values <code>sharded</code>, <code>legacy</code>, or <code>fallback</code>.</p></div></div></td><td><div><div><p>W-24179706</p></div></div></td></tr><tr><td><div><div><p>When API Gateway authenticates with Anypoint Platform, a transient failure of the <code>/login</code> request no longer discards an otherwise valid Access Management token. The token is now invalidated only on an actual authentication failure (401 or 403).</p></div></div></td><td><div><div><p>W-24144244</p></div></div></td></tr></tbody></table>

There is no DataWeave update for this version.

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## September 2026

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.34 includes Runtime Manager agent 2.7.16. See
  [Runtime Manager Agent 2.7.16 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-16).

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.

  - Health Signals: Evaluates a small set of fast host- and JVM-level health signals and reports
    those that triggered, including low memory, high CPU steal, and JVM crash logs.

  - Memory Detail: Provides a JVM memory-pool breakdown and garbage-collector statistics, showing
    heap and non-heap usage with metrics such as initial, used, committed, and maximum memory
    values.

  - Known Issues: Scans the runtime logs and deployed applications for well-known problem
    signatures, including out-of-memory conditions, abnormal terminations, and MUnit packaging
    issues.

### Fixed Issues

Patch release version: 4.6.34

This patch update addresses these Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>An <code>&lt;async&gt;</code> scope can now be configured to wait for its in-flight events to finish before flows are stopped during a graceful shutdown, which helps avoid dropped or canceled async work. This behavior is disabled by default and can be enabled through the <code>mule.async.gracefulShutdown.drainInflight</code> system property.</p></div></div></td><td><div><div><p>W-23602447</p></div></div></td></tr><tr><td><div><div><p>An SDK-based reconnectable message source no longer attempts to reconnect while a graceful shutdown is in progress.</p></div></div></td><td><div><div><p>W-23122573</p></div></div></td></tr><tr><td><div><div><p>Custom error mappings in the Tracing module are no longer lost on error propagation when an operation inside a <code>tracing:with-correlation-id</code> scope fails, which previously reverted the mapped error type to the raw connector error.</p></div></div></td><td><div><div><p>W-21815402</p></div></div></td></tr><tr><td><div><div><p>A memory leak no longer occurs when <code>parallel-foreach</code> and <code>scatter-gather</code> routes leave the route event pinned in a worker thread’s memory after route completion.</p></div></div></td><td><div><div><p>W-23829061</p></div></div></td></tr><tr><td><div><div><p>Artifact descriptor validation failures during deployment now report more specific exceptions.</p></div></div></td><td><div><div><p>W-23047228</p></div></div></td></tr><tr><td><div><div><p>Analytics events for requests rejected due to back-pressure are no longer incorrectly reported as HTTP 500 and now correctly report 503 by default. Custom status codes for other error scenarios can also be configured through the <code>anypoint.platform.error.mapping</code> (format <code>NAMESPACE:IDENTIFIER:STATUS_CODE</code>, comma-separated for multiple mappings) and <code>anypoint.platform.error.default</code> system properties.</p></div></div></td><td><div><div><p>W-23509148</p></div></div></td></tr><tr><td><div><div><p>API Gateway no longer fails to read shard checksums from an ETag header that contains commas.</p></div></div></td><td><div><div><p>W-23572494</p></div></div></td></tr><tr><td><div><div><p>The fix for idle connections being destroyed and recreated instead of reused when the number of idle connections reached the configured <code>maxIdle</code> limit under concurrent load, introduced in a previous release, is reverted in this release.</p></div></div></td><td><div><div><p>W-22716456</p></div></div></td></tr><tr><td><div><div><p>The jsoup library is upgraded to 1.23.1.</p></div></div></td><td><div><div><p>W-23715606</p></div></div></td></tr><tr><td><div><div><p>The Apache Commons Compress library is upgraded to 1.26.0.</p></div></div></td><td><div><div><p>W-3300013</p></div></div></td></tr><tr><td><div><div><p>The Jackson library is upgraded to 2.22.1.</p></div></div></td><td><div><div><p>W-23540335</p></div></div></td></tr><tr><td><div><div><p>The RAML Parser library is upgraded to 2-1.2.1.</p></div></div></td><td><div><div><p>W-23328350</p></div></div></td></tr><tr><td><div><div><p>The <code>com.mulesoft.mule.runtime.gw.api.analytics</code> package is now open to all modules, so the Runtime Manager agent can serialize analytics events.</p></div></div></td><td><div><div><p>W-23846531</p></div></div></td></tr></tbody></table>

DataWeave 2.6.30 is bundled with the Mule 4.6.34 release. This patch release addresses these
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>You can now configure the size of the DataWeave script parser cache by using the <code>mule.weave.script.parser.cache.size</code> system property.</p></div></div></td><td><div><div><p>W-23138851</p></div></div></td></tr><tr><td><div><div><p>A thread-safety livelock no longer occurs in the Java module builder and converter caches.</p></div></div></td><td><div><div><p>W-23652160</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## August 2026

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.33 includes Runtime Manager agent 2.7.18. See
  [Runtime Manager Agent 2.7.18 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-18).

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.

  - Network Info: Shows host-level network diagnostics, including the hostname, network interfaces
    with their assigned IP addresses and I/O counters, and active and listening network connections.

  - Agent Info: Reports the installation and health of the Mule agent that pairs the runtime with
    Anypoint Platform, including whether the agent is installed, its version, key configuration
    values, keystore certificate details, and the most recent connection status.

  - Platform Connectivity: Checks TCP connectivity from the Mule runtime host to the Anypoint
    Platform endpoints and dumps the TLS certificate chain presented by the platform.

### Fixed Issues

Patch release version: 4.6.33

This patch update addresses these Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Idle connections are no longer destroyed and recreated instead of being reused when the number of idle connections reaches the configured <code>maxIdle</code> limit under concurrent load.</p></div></div></td><td><div><div><p>W-22716456</p></div></div></td></tr><tr><td><div><div><p>A batch job no longer fails with a <code>MULE:CANCELLED</code> error during graceful shutdown.</p></div></div></td><td><div><div><p>W-23426859</p></div></div></td></tr><tr><td><div><div><p>Potential errors thrown during runtime shutdown are now handled correctly.</p></div></div></td><td><div><div><p>W-23051939</p></div></div></td></tr><tr><td><div><div><p>The Diagnostic Information Analysis File (DIAF) now includes network information.</p></div></div></td><td><div><div><p>W-22383655</p></div></div></td></tr><tr><td><div><div><p>The Diagnostic Information Analysis File (DIAF) now includes Mule agent information.</p></div></div></td><td><div><div><p>W-22383660</p></div></div></td></tr><tr><td><div><div><p>The Diagnostic Information Analysis File (DIAF) now includes a platform connectivity check.</p></div></div></td><td><div><div><p>W-22383679</p></div></div></td></tr><tr><td><div><div><p>The API gateway resource cache is enabled by default. You can now disable it by setting the <code>anypoint.platform.resource_cache_enabled</code> system property to <code>false</code>.</p></div></div></td><td><div><div><p>W-23542185</p></div></div></td></tr><tr><td><div><div><p>The Jackson library is upgraded to 2.22.0.</p></div></div></td><td><div><div><p>W-23121654</p></div></div></td></tr></tbody></table>

DataWeave 2.6.29 is bundled with the Mule 4.6.33 release. This patch release addresses these
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The repeated attribute selector (<code>.*@</code>) now correctly preserves values when processing data structures containing empty map slots.</p></div></div></td><td><div><div><p>W-23457314</p></div></div></td></tr><tr><td><div><div><p>The Jackson library is upgraded to 2.21.5.</p></div></div></td><td><div><div><p>W-23037592</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## July 2026

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.32 includes Runtime Manager agent 2.7.16. See
  [Runtime Manager Agent 2.7.16 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-16).

Feature Flagging Mechanism:

- Mule 4.6 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.6.32

This patch update addresses these Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>A <code>NullPointerException</code> error no longer occurs in event context handling when a flow times out while a non-blocking operation is still in flight.</p></div></div></td><td><div><div><p>W-22902839</p></div></div></td></tr><tr><td><div><div><p>Cluster node IDs are no longer generated with negative values.</p></div></div></td><td><div><div><p>W-22294724</p></div></div></td></tr><tr><td><div><div><p>Graceful shutdown no longer times out when a global error handler runs for a flow.</p></div></div></td><td><div><div><p>W-22434375</p></div></div></td></tr><tr><td><div><div><p>Long-running internal tasks no longer use the shared <code>forkJoin</code> pool during parallel flow shutdown and bootstrap configuration, preventing thread starvation.</p></div></div></td><td><div><div><p>W-22279521</p></div></div></td></tr><tr><td><div><div><p>Duplicate XSD elements are no longer generated for connection providers declared at both the extension and configuration levels.</p></div></div></td><td><div><div><p>W-20824537</p></div></div></td></tr><tr><td><div><div><p>Shutdown validation for dynamic configurations can now be skipped by enabling the <code>mule.forcefulShutdown.dynamicConfig.disableStoppingCheck</code> system property.</p></div></div></td><td><div><div><p>W-22772644</p></div></div></td></tr><tr><td><div><div><p>Flows with a scheduler source are no longer left in an invalid state after a flow restart.</p></div></div></td><td><div><div><p>W-22918240</p></div></div></td></tr><tr><td><div><div><p>Stopping a flow no longer waits unnecessarily when no events are being processed.</p></div></div></td><td><div><div><p>W-22969411</p></div></div></td></tr><tr><td><div><div><p>Project versions defined with properties are now resolved recursively.</p></div></div></td><td><div><div><p>W-22845430</p></div></div></td></tr><tr><td><div><div><p>Extension packager validation no longer fails for operations annotated with <code>@Validator</code> that use a <code>CompletionCallback</code> operation.</p></div></div></td><td><div><div><p>W-22817376</p></div></div></td></tr><tr><td><div><div><p>The Netty HTTP listener now rejects <code>HTTP/1.1</code> requests that have a missing or duplicate Host header, in compliance with RFC 9112.</p></div></div></td><td><div><div><p>W-23052713</p></div></div></td></tr><tr><td><div><div><p>SDK sources that don’t implement <code>Reconnectable</code> are no longer restarted during graceful shutdown.</p></div></div></td><td><div><div><p>W-21563258</p></div></div></td></tr><tr><td><div><div><p>The maximum size of the dynamic <code>flow-ref</code> cache is now configurable through the <code>mule.flowRef.dynamicCacheMaxSize</code> system property, which defaults to 20.</p></div></div></td><td><div><div><p>W-22219018</p></div></div></td></tr><tr><td><div><div><p>Sensitive headers are no longer forwarded when an HTTP request is redirected to a different host. This can be configured with <code>FILTER_SENSITIVE_HEADERS_ON_REDIRECT</code>.</p></div></div></td><td><div><div><p>W-21045658</p></div></div></td></tr><tr><td><div><div><p>API Gateway contract persistence can now be disabled by setting the <code>anypoint.platform.contracts_persistence_enabled</code> system property to <code>false</code>, avoiding errors when persisting large numbers of contracts.</p></div></div></td><td><div><div><p>W-22568982</p></div></div></td></tr><tr><td><div><div><p>The Joda-Time library is upgraded to 2.13.0.</p></div></div></td><td><div><div><p>W-3300013</p></div></div></td></tr><tr><td><div><div><p>The Rhino library is upgraded to 1.7.15.1.</p></div></div></td><td><div><div><p>W-22805996</p></div></div></td></tr><tr><td><div><div><p>The Apache Neethi library is upgraded to 3.2.1.</p></div></div></td><td><div><div><p>W-22805997</p></div></div></td></tr><tr><td><div><div><p>The OpenTelemetry API library is upgraded to 1.62.0.</p></div></div></td><td><div><div><p>W-22806011</p></div></div></td></tr><tr><td><div><div><p>The Apache CXF library is upgraded to 3.5.11.</p></div></div></td><td><div><div><p>W-23037585</p></div></div></td></tr><tr><td><div><div><p>The c3p0 library is upgraded to 0.14.1.</p></div></div></td><td><div><div><p>W-23012711</p></div></div></td></tr><tr><td><div><div><p>The Bitronix Transaction Manager library is upgraded to 2.1.21.</p></div></div></td><td><div><div><p>W-22405007</p></div></div></td></tr></tbody></table>

DataWeave 2.6.28 is bundled with the Mule 4.6.32 release. This patch release addresses these
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Scope resolution errors no longer occur when importing Java classes with self-referential array properties.</p></div></div></td><td><div><div><p>W-22914494</p></div></div></td></tr><tr><td><div><div><p>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 <code>per_app_java_bean_cache</code> compatibility flag.</p></div></div></td><td><div><div><p>W-22417507</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## June 2026

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.31 includes Runtime Manager agent 2.7.15. See
  [Runtime Manager Agent 2.7.15 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-15).

### Fixed Issues

Patch release version: 4.6.31

This patch update addresses these Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Connectivity testing of configurations in clustered deployments no longer uses distributed locks, preventing deadlocks.</p></div></div></td><td><div><div><p>W-22248198</p></div></div></td></tr><tr><td><div><div><p>Fatal errors such as <code>StackOverflowError</code> are now logged instead of being consumed by internal error handling.</p></div></div></td><td><div><div><p>W-22496803</p></div></div></td></tr><tr><td><div><div><p>Mule no longer hangs during shutdown when a parameter validation exception occurs during flow execution.</p></div></div></td><td><div><div><p>W-22248534</p></div></div></td></tr><tr><td><div><div><p>Race conditions in <code>outerFluxCompletionScheduler</code> no longer occur during graceful shutdown.</p></div></div></td><td><div><div><p>W-22343018</p></div></div></td></tr><tr><td><div><div><p>The ObjectStore retrieved from the Registry in <code>OAuthHandler</code> is now properly initialized and started.</p></div></div></td><td><div><div><p>W-22373641</p></div></div></td></tr><tr><td><div><div><p>SDK parameter validation errors now raise the <code>MULE:VALIDATION</code> error type instead of <code>MULE:UNKNOWN</code>.</p></div></div></td><td><div><div><p>W-22276522</p></div></div></td></tr><tr><td><div><div><p>Race conditions during policy redeployment that caused Mule to stop processing events permanently no longer occur.</p></div></div></td><td><div><div><p>W-22343705</p></div></div></td></tr><tr><td><div><div><p><code>ConcurrentModificationException</code> errors no longer occur when multiple plugins with shared dependencies are deployed simultaneously.</p></div></div></td><td><div><div><p>W-21193046</p></div></div></td></tr><tr><td><div><div><p>Cluster encryption now uses the configured algorithm correctly instead of defaulting to Blowfish.</p></div></div></td><td><div><div><p>W-21666905</p></div></div></td></tr><tr><td><div><div><p>The error type in the EE Cache scope is now correctly reported as <code>MULE:RETRY_EXHAUSTED</code> instead of <code>EE:RETRY_EXHAUSTED</code> when until-successful exhausts its retries.</p></div></div></td><td><div><div><p>W-21525972</p></div></div></td></tr><tr><td><div><div><p>Large Anypoint Platform authentication failure responses no longer cause excessive log bloat.</p></div></div></td><td><div><div><p>W-21882516</p></div></div></td></tr><tr><td><div><div><p>In-memory Object Store partitions now correctly use cluster-wide storage when deployed to a cluster with the Object Store plugin enabled.</p></div></div></td><td><div><div><p>W-17714668</p></div></div></td></tr><tr><td><div><div><p>Persistent ObjectStore or Batch data serialized before a patch upgrade now deserializes correctly after upgrading.</p></div></div></td><td><div><div><p>W-22623626</p></div></div></td></tr><tr><td><div><div><p><code>OutOfMemory</code> errors no longer occur when establishing SSL connections with HTTP endpoints.</p></div></div></td><td><div><div><p>W-22547971</p></div></div></td></tr></tbody></table>

DataWeave 2.6.27 is bundled with the Mule 4.6.31 release. This patch release addresses these
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>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 <code>per_app_java_bean_cache</code> compatibility flag.</p></div></div></td><td><div><div><p>W-22417507</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## May 2026

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.30 includes Runtime Manager agent 2.7.13. See
  [Runtime Manager Agent 2.7.13 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-13).

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.6.30

This patch update addresses these Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Configuration references to configs defined in a parent domain are now properly validated at deployment time, preventing unclear runtime errors.</p></div></div></td><td><div><div><p>W-11453332</p></div></div></td></tr><tr><td><div><div><p>Extension operations using <code>@Content</code> parameters with complex map structures no longer fail to deploy.</p></div></div></td><td><div><div><p>W-18034452</p></div></div></td></tr><tr><td><div><div><p>The Grizzly HTTP library is upgraded to 2.3.36-MULE-029.</p></div></div></td><td><div><div><p>W-21337433</p></div></div></td></tr><tr><td><div><div><p>The plexus-utils library is upgraded to 4.0.3.</p></div></div></td><td><div><div><p>W-21774430</p></div></div></td></tr><tr><td><div><div><p>A memory leak in dynamic <code>flow-ref</code> resolution that could eventually lead to an <code>OutOfMemoryError</code> no longer occurs.</p></div></div></td><td><div><div><p>W-22013292</p></div></div></td></tr><tr><td><div><div><p>Deserialization errors no longer occur in Redis-backed Object Stores when accessing cached data created on an earlier Mule runtime version.</p></div></div></td><td><div><div><p>W-20880559</p></div></div></td></tr><tr><td><div><div><p>API Gateway contracts for public OAuth clients using PKCE are no longer dropped when the client secret is null.</p></div></div></td><td><div><div><p>W-21177224</p></div></div></td></tr><tr><td><div><div><p>The support-tools-installer is removed from the Mule runtime distribution.</p></div></div></td><td><div><div><p>W-21842339</p></div></div></td></tr></tbody></table>

DataWeave 2.6.26 is bundled with the Mule 4.6.30 release. This patch release addresses these
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p><code>atBeginningOfDay</code> now returns the midnight offset on DST days, instead of the input offset.</p></div></div></td><td><div><div><p>W-21614817</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## April 2026

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.29 includes Runtime Manager agent 2.7.11. See
  [Runtime Manager Agent 2.7.11 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-11).

Feature Flagging Mechanism:

- Mule 4.6 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.6.29

This patch update addresses these Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The c3p0 library is upgraded to 0.12.0.</p></div></div></td><td><div><div><p>W-21391116</p></div></div></td></tr><tr><td><div><div><p>The mchange-commons-java library is upgraded to 0.4.0.</p></div></div></td><td><div><div><p>W-21391115</p></div></div></td></tr><tr><td><div><div><p><code>NullPointerException</code> 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 <code>dispose()</code> and <code>cancel()</code>.</p></div></div></td><td><div><div><p>W-20256082</p></div></div></td></tr><tr><td><div><div><p>Until Successful scopes no longer continue retrying during application shutdown when using flow-ref.</p></div></div></td><td><div><div><p>W-20267296</p></div></div></td></tr><tr><td><div><div><p><code>NullPointerException: No Context at location</code> errors no longer occur when using operation policies with routers or scopes.</p></div></div></td><td><div><div><p>W-20791354</p></div></div></td></tr><tr><td><div><div><p>OAuth token storage now correctly uses custom <code>ObjectStores</code> (such as Redis) configured through the Object Store parameter when they’re registered in the application registry instead of the <code>ObjectStoreManager</code>.</p></div></div></td><td><div><div><p>W-19811593</p></div></div></td></tr><tr><td><div><div><p><code>Exception reached subscriber</code> errors no longer occur when combining interceptors and operation policies.</p></div></div></td><td><div><div><p>W-21250126</p></div></div></td></tr><tr><td><div><div><p>Scheduler jobs no longer deadlock during flow shutdown.</p></div></div></td><td><div><div><p>W-21263748</p></div></div></td></tr><tr><td><div><div><p>TLS Context can now be initialized during application deployment by using the <code>mule.enable.inline.tls.context.initialization</code> feature flag.</p></div></div></td><td><div><div><p>W-20038933</p></div></div></td></tr></tbody></table>

DataWeave 2.6.25 is bundled with the Mule 4.6.29 release. This patch release addresses these
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The Avro library is upgraded to 1.12.1. The Jackson Core library is upgraded to 2.21.1.</p></div></div></td><td><div><div><p>W-21415439</p></div></div></td></tr><tr><td><div><div><p>The Jakarta Mail library is upgraded to 2.1.5.</p></div></div></td><td><div><div><p>W-21320250</p></div></div></td></tr><tr><td><div><div><p>The range operator now returns null for invalid ranges.</p></div></div></td><td><div><div><p>W-21781423</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## March 2026

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.28 includes Runtime Manager agent 2.7.10. See
  [Runtime Manager Agent 2.7.10 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-10).

Feature Flagging Mechanism:

- Mule 4.6 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.6.28

This patch update addresses these Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>When the <code>mule.forcefulShutdown.dynamicConfig.disableStoppingCheck</code> system property is enabled, the dynamic configuration check is disabled during graceful shutdown.</p></div></div></td><td><div><div><p>W-20890587</p></div></div></td></tr><tr><td><div><div><p>When the <code>mule.forcefulShutdown.raiseCancelledError</code> feature flag is enabled, Mule runtime now raises a <code>MULE:CANCELLED</code> error instead of a <code>MULE:UNKNOWN</code> error if it attempts to create a dynamic configuration during shutdown.</p></div></div></td><td><div><div><p>W-20890613</p></div></div></td></tr><tr><td><div><div><p>Extensions no longer export <code>mule-sdk-api</code> and <code>jakarta</code> dependencies in the <code>mule-artifact.json</code> file.</p></div></div></td><td><div><div><p>W-21001749</p></div></div></td></tr><tr><td><div><div><p>Public flows now stop concurrently during graceful shutdown.</p></div></div></td><td><div><div><p>W-21228085</p></div></div></td></tr><tr><td><div><div><p>Deadlocks no longer occur during log reconfiguration when policies are applied.</p></div></div></td><td><div><div><p>W-21231834</p></div></div></td></tr><tr><td><div><div><p>When the <code>mule.enableLogEventDumpOnShutdown</code> system property is enabled, the event dump is now logged during application shutdown.</p></div></div></td><td><div><div><p>W-21232374</p></div></div></td></tr><tr><td><div><div><p>The <code>"java.lang.IllegalStateException: The client must be started before use."</code> error no longer occurs when requesting an OAuth access token.</p></div></div></td><td><div><div><p>W-17689958</p></div></div></td></tr><tr><td><div><div><p>When the <code>mule.propagate.objectStore.customization.to.policies</code> feature flag is enabled, policies now respect their configured TTL when using Object Store v2.</p></div></div></td><td><div><div><p>W-21215761</p></div></div></td></tr><tr><td><div><div><p>The tika-core library is upgraded to 3.2.3.</p></div></div></td><td><div><div><p>W-21179465</p></div></div></td></tr><tr><td><div><div><p>The <code>"API is blocked (unavailable)"</code> log message no longer appears during policy updates without a corresponding unblocked message.</p></div></div></td><td><div><div><p>W-20633888</p></div></div></td></tr><tr><td><div><div><p>APIkit flows that use non-default names and are mapped through the <code>flow-mapping</code> parameter on <code>apikit:config</code> are now correctly counted as public flows instead of being treated as private.</p></div></div></td><td><div><div><p>W-18668900</p></div></div></td></tr></tbody></table>

DataWeave 2.6.24 is bundled with the Mule 4.6.28 release. This patch release addresses these
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The Array range selector operator no longer experiences performance degradation.</p></div></div></td><td><div><div><p>W-20220578</p></div></div></td></tr><tr><td><div><div><p>Concurrent access to <code>KeyValuePairs</code> inside lazy materialized objects no longer causes unexpected behavior.</p></div></div></td><td><div><div><p>W-21045501</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## February 2026

### Patch 4.6.27

- This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990.

### Patch 4.6.26

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.26 includes Runtime Manager agent 2.7.9. See
  [Runtime Manager Agent 2.7.9 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-9).

### Fixed Issues

Patch release version: 4.6.26

This patch update addresses these Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>JDK Flight Recorder (JFR) is now disabled by default.</p></div></div></td><td><div><div><p>W-19990145</p></div></div></td></tr><tr><td><div><div><p>The Abstract Syntax Tree (AST) file of applications using the until-successful component is now leveraged by Mule runtime instead of parsing the configuration XML files.</p></div></div></td><td><div><div><p>W-20283146</p></div></div></td></tr><tr><td><div><div><p>Mule application unresponsiveness no longer occurs after a policy that uses the until-successful component is undeployed or redeployed.</p></div></div></td><td><div><div><p>W-20628990</p></div></div></td></tr><tr><td><div><div><p>Implemented minor improvements to Mule classloading structures to enhance efficiency and stability.</p></div></div></td><td><div><div><p>W-20028988</p></div></div></td></tr><tr><td><div><div><p>Thread Context Classloader (TCCL) is no longer wrongly set to the connector after an operation policy <code>execute-next</code>.</p></div></div></td><td><div><div><p>W-20618734</p></div></div></td></tr><tr><td><div><div><p>Fastutil is now replaced with fastutil-core.</p></div></div></td><td><div><div><p>W-20729870</p></div></div></td></tr></tbody></table>

There is no DataWeave update for this version.

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## January 2026

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.25 includes Runtime Manager agent 2.7.9. See
  [Runtime Manager Agent 2.7.9 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-9).

MUnit:

- MUnit version 3.6.3 is now required. See
  [MUnit 3.6.3 Release Notes](https://docs.mulesoft.com/release-notes/munit/munit-3.6.3-release-notes).

General improvements:

- You can now view deployment information in the `diaf` file. See
  [Mule Troubleshooting Plugin](https://docs.mulesoft.com/mule-runtime/latest/mule-troubleshooting-plugin) for more
  information.

### Fixed Issues

Patch release version: 4.6.25

This patch update addresses these Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Batch jobs no longer hang when errors occur in steps that use try scopes with global error handlers.</p></div></div></td><td><div><div><p>W-17738563</p></div></div></td></tr><tr><td><div><div><p>Design-time operations on primary content parameters with non-Java types now work correctly.</p></div></div></td><td><div><div><p>W-20187776</p></div></div></td></tr><tr><td><div><div><p>Logging information is now improved during graceful shutdown.</p></div></div></td><td><div><div><p>W-20278970</p></div></div></td></tr><tr><td><div><div><p>A deadlock between Log4j Mule log support during application initialization no longer occurs.</p></div></div></td><td><div><div><p>W-20419795</p></div></div></td></tr><tr><td><div><div><p>MUnit tests no longer fail intermittently when running on Java 17.</p></div></div></td><td><div><div><p>W-17044721</p></div></div></td></tr><tr><td><div><div><p>Batch processing no longer fails with serialization error when LDAP action throws an error in Java 17.</p></div></div></td><td><div><div><p>W-19524600</p></div></div></td></tr><tr><td><div><div><p>Dynamic configurations now work correctly during initialization when using <code>hashCode</code> and <code>equals</code> methods on a <code>TLSConfiguration</code> class.</p></div></div></td><td><div><div><p>W-18835469</p></div></div></td></tr></tbody></table>

DataWeave 2.6.22 is bundled with the Mule 4.6.25 release. This patch release addresses these
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The stream reader now processes input with multi-byte characters correctly.</p></div></div></td><td><div><div><p>W-20016549</p></div></div></td></tr><tr><td><div><div><p>The org.apache.commons:commons-text library is upgraded to 1.14.0.</p></div></div></td><td><div><div><p>W-20618375</p></div></div></td></tr><tr><td><div><div><p>Each variable is now extracted from <code>vars</code>, allowing its materialization to be managed individually. The <code>mule.dw.enable_vars_materialization_pass</code> compatibility flag is added to preserve the previous materialization behavior.</p></div></div></td><td><div><div><p>W-19580992 / W-17167283</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## November 2025

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.24 includes Runtime Manager agent 2.7.8. See
  [Runtime Manager Agent 2.7.8 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-8).

General improvements:

- You can now view CPU usage information in the `diaf` file. See
  [Mule Troubleshooting Plugin](https://docs.mulesoft.com/mule-runtime/latest/mule-troubleshooting-plugin) for more
  information.

### Fixed Issues

Patch release version: 4.6.24

This patch update addresses these Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>OpenTelemetry current API sampling decisions now propagate correctly through <code>http:requester</code> calls to downstream APIs.</p></div></div></td><td><div><div><p>W-19784910</p></div></div></td></tr><tr><td><div><div><p><code>UndeclaredThrowableException</code> errors no longer occur during Bitronix reconnection.</p></div></div></td><td><div><div><p>W-15196888</p></div></div></td></tr><tr><td><div><div><p><code>InaccessibleObjectException</code> errors no longer occur during deployment when the <code>mule.classloading.verbose</code> property is set.</p></div></div></td><td><div><div><p>W-18563387</p></div></div></td></tr><tr><td><div><div><p>MDC information is now properly preserved when using loggers inside custom Java code invoked from a DataWeave script.</p></div></div></td><td><div><div><p>W-18912999</p></div></div></td></tr><tr><td><div><div><p>Batch queuestore files now clean up correctly in rare load failure scenarios such as out-of-memory errors.</p></div></div></td><td><div><div><p>W-17935223</p></div></div></td></tr><tr><td><div><div><p>Builds no longer fail when running tests from an extension that uses Mule SDK with Java 8 through Java 17.</p></div></div></td><td><div><div><p>W-18964335</p></div></div></td></tr><tr><td><div><div><p>The until-successful scope now properly honors the graceful shutdown timeout. In versions earlier than 4.11.0, you must enable this behavior using these system properties: <code>mule.untilSuccessful.retryOnCriticalError.disallow=true</code> and <code>mule.forcefulShutdown.raiseCancelledError=true</code>.</p></div></div></td><td><div><div><p>W-19340663</p></div></div></td></tr><tr><td><div><div><p>Hashing now uses <code>toHex</code> 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.6, set the <code>mule.redeliveryPolicy.encode.secureHash</code> system property to <code>true</code>.</p></div></div></td><td><div><div><p>W-18584560</p></div></div></td></tr><tr><td><div><div><p><code>IllegalAccessException</code> no longer thrown when DW serializes <code>error.errorMessage</code> in Scatter-Gather error route.</p></div></div></td><td><div><div><p>W-19340663</p></div></div></td></tr><tr><td><div><div><p>Mule applications that use TLS KeyStore configurations no longer fail to deploy with “NO MODEL RESOLVED” warnings and <code>ConfigurationException</code> errors.</p></div></div></td><td><div><div><p>W-16565012</p></div></div></td></tr><tr><td><div><div><p>Mule Troubleshooting Plugin executions no longer fail when the IP address changes.</p></div></div></td><td><div><div><p>W-19802474</p></div></div></td></tr></tbody></table>

DataWeave 2.6.20 is bundled with the Mule 4.6.24 release. This patch release addresses these
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The Apache Commons Lang dependency is removed from the distribution.</p></div></div></td><td><div><div><p>W-19803454</p></div></div></td></tr><tr><td><div><div><p>Materialization errors no longer occur when running functions.</p></div></div></td><td><div><div><p>W-19884071</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## October 2025

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.23 includes Runtime Manager agent 2.7.7. See
  [Runtime Manager Agent 2.7.7 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-7).

Mule Troubleshooting Plugin:

- Mule 4.6.23 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](https://docs.mulesoft.com/mule-runtime/latest/mule-troubleshooting-plugin) for more
  information.

### Fixed Issues

Patch release version: 4.6.23

This patch update addresses these Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The org.springframework library is upgraded to 5.3.45.</p></div></div></td><td><div><div><p>W-18603096</p></div></div></td></tr><tr><td><div><div><p>Memory leaks no longer occur when a reconnection is configured in a Mule domain and referenced from multiple applications.</p></div></div></td><td><div><div><p>W-17857080</p></div></div></td></tr><tr><td><div><div><p><code>InaccessibleObjectException</code> errors no longer occur when using cluster mode on Java 17.</p></div></div></td><td><div><div><p>W-18667744</p></div></div></td></tr><tr><td><div><div><p>Fork-join routers no longer create unnecessary schedules when the timeout is set to infinite.</p></div></div></td><td><div><div><p>W-18347293</p></div></div></td></tr><tr><td><div><div><p>Potential deadlocks during deployment no longer occur when using some custom Log4j appenders.</p></div></div></td><td><div><div><p>W-19675881</p></div></div></td></tr><tr><td><div><div><p>This release reverts the changes introduced in W-17340911.</p></div></div></td><td><div><div><p>W-17340911</p></div></div></td></tr><tr><td><div><div><p>Cookies now propagate correctly across multiple redirect scenarios.</p></div></div></td><td><div><div><p>W-18971065</p></div></div></td></tr><tr><td><div><div><p>Batch queuestore files now clean up correctly in rare load failure scenarios, such as out of memory errors.</p></div></div></td><td><div><div><p>W-17935223</p></div></div></td></tr><tr><td><div><div><p>Gatekeeper deadlock errors no longer occur during race conditions among contract downloads and policy application.</p></div></div></td><td><div><div><p>W-19407164</p></div></div></td></tr></tbody></table>

DataWeave 2.6.19 is bundled with the Mule 4.6.23 release. This patch release addresses these
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The <code>take</code> function now works with streaming when argument is larger than the array length.</p></div></div></td><td><div><div><p>W-19168279</p></div></div></td></tr><tr><td><div><div><p><code>java-module</code> now supports object fields access when using different capitalizations.</p></div></div></td><td><div><div><p>W-19477334</p></div></div></td></tr><tr><td><div><div><p>Module compilation performance is improved when running concurrently.</p></div></div></td><td><div><div><p>W-19376546</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## September 2025

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.22 includes Runtime Manager agent 2.7.7. See
  [Runtime Manager Agent 2.7.7 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-7).

### Fixed Issues

Patch release version: 4.6.22

This patch update addresses the following Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>TLS configuration for FIPS-140-2 is now upgraded.</p></div></div></td><td><div><div><p>W-16315176</p></div></div></td></tr><tr><td><div><div><p>Applications using Scheduler component in a strict FIPS-140-2 environment no longer fail to deploy due to the unavailability of the MD5 algorithm.</p></div></div></td><td><div><div><p>W-19319437</p></div></div></td></tr><tr><td><div><div><p>OAuth token is now refreshed when used through <code>ExtensionClient</code>.</p></div></div></td><td><div><div><p>W-19248279</p></div></div></td></tr></tbody></table>

There is no DataWeave update for this version.

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## August 2025

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.21 includes Runtime Manager agent 2.7.6. See
  [Runtime Manager Agent 2.7.6 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-6).

General improvements:

- License Delivery Update: Starting with Mule 4.6.21, Enterprise licenses are now provided either as
  a single `license.lic` file or as a `.zip` that contains both FIPS and non-FIPS licenses. See
  [FIPS 140-2 Compliance Support](https://docs.mulesoft.com/mule-runtime/latest/fips-140-2-compliance-support) for
  details.

General improvements:

- When running Mule runtime in FIPS security mode with clustering enabled, the encryption key
  defined in `mule.cluster.network.encryption.key` must have a length of 16, 24, or 32 bytes. See
  [Enable Clustering in FIPS Mode](https://docs.mulesoft.com/on-premises/latest/mule-high-availability-ha-clusters#cluster_fips)
  for details.

### Fixed Issues

Patch release version: 4.6.21

This patch update addresses the following Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Silent errors and hangs no longer occur when a component fails to start within a foreach/subflow combination.</p></div></div></td><td><div><div><p>W-18589595</p></div></div></td></tr><tr><td><div><div><p>An incorrect error level message no longer shows during deployment when using APIKit with no flow mappings.</p></div></div></td><td><div><div><p>W-19004884</p></div></div></td></tr><tr><td><div><div><p>Performance degradation no longer occurs when using repeatable streaming.</p></div></div></td><td><div><div><p>W-19175330</p></div></div></td></tr></tbody></table>

DataWeave 2.6.17 is bundled with the Mule 4.6.21 release. This patch release addresses the following
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>A <code>stackOverflowException</code> error no longer occurs during materialization.</p></div></div></td><td><div><div><p>W-18981240</p></div></div></td></tr><tr><td><div><div><p>The <code>distinctBy</code> function in <code>dw::core::Core</code> now works as expected when used with a CSV input.</p></div></div></td><td><div><div><p>W-18990604</p></div></div></td></tr><tr><td><div><div><p>DataWeave runtime types are now correctly written when outputting Java.</p></div></div></td><td><div><div><p>W-18942349</p></div></div></td></tr><tr><td><div><div><p>Access to multipart content raw value no longer reads the part content.</p></div></div></td><td><div><div><p>W-18892158</p></div></div></td></tr><tr><td><div><div><p>The <code>sizeOf</code> function now works correctly in DataWeave 2.6.14 and later.</p></div></div></td><td><div><div><p>W-18850597</p></div></div></td></tr><tr><td><div><div><p>The <code>orderBy</code> function now evaluates ordering criteria only when required.</p></div></div></td><td><div><div><p>W-18851259</p></div></div></td></tr><tr><td><div><div><p>The <code>fromCharCode</code> function now works as expected.</p></div></div></td><td><div><div><p>W-17204482</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## July 2025

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.20 includes Runtime Manager agent 2.7.5. See
  [Runtime Manager Agent 2.7.5 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-5).

### Fixed Issues

Patch release version: 4.6.20

This patch update addresses the following Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Schedulers are no longer triggered during graceful shutdown.</p></div></div></td><td><div><div><p>W-17981248</p></div></div></td></tr><tr><td><div><div><p>The commons-beanutils:commons-beanutils library is upgraded to v1.11.0.</p></div></div></td><td><div><div><p>W-18687846</p></div></div></td></tr><tr><td><div><div><p>The com.google.code.gson:gson library is upgraded to v2.12.1.</p></div></div></td><td><div><div><p>W-17896347</p></div></div></td></tr><tr><td><div><div><p>Repeatable streams now make data available before the buffer is full. To enable this behavior, set the system property <code>mule.repeatableStreaming.bytes.eagerRead</code> to <code>true</code>.</p></div></div></td><td><div><div><p>W-18716253</p></div></div></td></tr><tr><td><div><div><p>Serialization now works correctly with API Gateway internal classes.</p></div></div></td><td><div><div><p>W-18475283</p></div></div></td></tr><tr><td><div><div><p>The W-17340911 fix, which resolved loader constraint violation errors related to <code>http-connector</code> dependencies in both the domain and the policy, has now been reverted to restore the previous behavior.</p></div></div></td><td><div><div><p>W-18327141</p></div></div></td></tr></tbody></table>

DataWeave 2.6.16 is bundled with the Mule 4.6.20 release. This patch release addresses the following
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>This patch update reverts the fix.</p></div></div></td><td><div><div><p>W-17167283</p></div></div></td></tr><tr><td><div><div><p>XML encoding detection now works correctly when the declaration header is missing.</p></div></div></td><td><div><div><p>W-18853667</p></div></div></td></tr><tr><td><div><div><p>The <code>fromCharCode</code> function in <code>dw::core::Strings.</code> now manages surrogate characters correctly.</p></div></div></td><td><div><div><p>W-17204482</p></div></div></td></tr><tr><td><div><div><p>Unicode characters now render correctly at the beginning of the string when using the DataWeave <code>writer</code> function with the <code>onlyData</code> flag enabled.</p></div></div></td><td><div><div><p>W-14855645</p></div></div></td></tr><tr><td><div><div><p>The Apache POI library is now upgraded.</p></div></div></td><td><div><div><p>W-18253747</p></div></div></td></tr><tr><td><div><div><p>Experimental warning messages are no longer logged on DataWeave SDK files.</p></div></div></td><td><div><div><p>W-16384926</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## June 2025

### Patch 4.6.19

- This patch update reverts the fixes for the following Mule issue: W-17703164

### Patch 4.6.18

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.18 includes Runtime Manager agent 2.7.4. See
  [Runtime Manager Agent 2.7.4 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-4).

### Fixed Issues

Patch release version: 4.6.18

This patch update addresses the following Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Loader constraint violation errors no longer occur when <code>http-connector</code> dependencies exist in both the domain and the policy.</p></div></div></td><td><div><div><p>W-17340911</p></div></div></td></tr><tr><td><div><div><p>Serialization of result objects with Kryo no longer fails with <code>InaccessibleObjectException</code> in Java 17.</p></div></div></td><td><div><div><p>W-17774685</p></div></div></td></tr><tr><td><div><div><p>Class loading no longer results in deadlocks caused by a race condition.</p></div></div></td><td><div><div><p>W-18388443</p></div></div></td></tr><tr><td><div><div><p>Spring Framework artifacts are replaced with vendor-supported equivalents to improve long-term compatibility.</p></div></div></td><td><div><div><p>W-18462316</p></div></div></td></tr><tr><td><div><div><p>A serialization exception no longer occurs when using caching scope.</p></div></div></td><td><div><div><p>W-17703164</p></div></div></td></tr></tbody></table>

DataWeave 2.6.15 is bundled with the Mule 4.6.18 release. This patch release addresses the following
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The performance of the <code>orderBy</code> function is now improved.</p></div></div></td><td><div><div><p>W-18439576</p></div></div></td></tr><tr><td><div><div><p>Reading a CSV file inside a MultiPart body now works correctly when performed more than once.</p></div></div></td><td><div><div><p>W-17147598</p></div></div></td></tr><tr><td><div><div><p>A memory leak of the binding context no longer occurs when using the <code>foreach</code> scope.</p></div></div></td><td><div><div><p>W-18472194</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## May 2025

### Patch 4.6.17

The May patch update 4.6.17 addresses a regression in the previous May patch update, 4.6.16, and
includes the fixes in the patch.

Patch release version: 4.6.17

This patch update addresses the following Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>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.</p></div></div></td><td><div><div><p>W-18528551</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

### Patch 4.6.16

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.16 includes Runtime Manager agent 2.7.2. See
  [Runtime Manager Agent 2.7.2 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-2).

### Fixed Issues

Patch release version: 4.6.16

This patch update addresses the following Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Parallel For Each events no longer randomly timeout after a <code>NullPointerException</code> error.</p></div></div></td><td><div><div><p>W-17980769</p></div></div></td></tr><tr><td><div><div><p>The error message "Couldn’t parse instance of ReentrantReadWriteLock" in ReentrantReadWriteLockSerializer no longer occurs.</p></div></div></td><td><div><div><p>W-18057570</p></div></div></td></tr><tr><td><div><div><p>Parameters field isn’t serialized in <code>InternalEventImplementation</code>.</p></div></div></td><td><div><div><p>W-17703164</p></div></div></td></tr><tr><td><div><div><p>Connectivity tests in MTS are now fixed for Java 17.</p></div></div></td><td><div><div><p>W-18075077</p></div></div></td></tr><tr><td><div><div><p>Exceptions no longer occur when using WebSocket close codes outside a predefined subset. The code now correctly handles all standard or custom WebSocket close codes.</p></div></div></td><td><div><div><p>W-17846088</p></div></div></td></tr><tr><td><div><div><p>The <code>expressionExecutor</code> in adapter is no longer disposed more than once.</p></div></div></td><td><div><div><p>W-16263266</p></div></div></td></tr><tr><td><div><div><p>org.glassfish:jakarta.json was removed form the distribution.</p></div></div></td><td><div><div><p>W-17896357</p></div></div></td></tr><tr><td><div><div><p>xerces-j is upgraded to 2.12.2.</p></div></div></td><td><div><div><p>W-16980865</p></div></div></td></tr><tr><td><div><div><p>raml-parser is upgraded to v1.0.44-17.</p></div></div></td><td><div><div><p>W-17750714</p></div></div></td></tr></tbody></table>

DataWeave 2.6.14 is bundled with the Mule 4.6.16 release. This patch release addresses the following
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Materialization issues no longer occur when using CSV content inside variables.</p></div></div></td><td><div><div><p>W-17167283</p></div></div></td></tr><tr><td><div><div><p>A compatibility flag is now added to address the different results produced by calling <code>sizeOf</code> with <code>NumberType</code>.</p></div></div></td><td><div><div><p>W-18020856</p></div></div></td></tr><tr><td><div><div><p>An unnecessary import is now removed from <code>dw::util::Diff</code> to eliminate a warning when running MUnit.</p></div></div></td><td><div><div><p>W-17670504</p></div></div></td></tr><tr><td><div><div><p>DataWeave no longer returns a format error on <code>readUnquotedString</code>.</p></div></div></td><td><div><div><p>W-18118138</p></div></div></td></tr><tr><td><div><div><p>Overflowing no longer occurs while reading large file on multipart format.</p></div></div></td><td><div><div><p>W-17644871</p></div></div></td></tr><tr><td><div><div><p>Performance issues no longer occur when using the Mule API Java class Message in DataWeave scripts.</p></div></div></td><td><div><div><p>W-18034217</p></div></div></td></tr><tr><td><div><div><p>DataWeave now preserves trailing zeroes of single-element sum.</p></div></div></td><td><div><div><p>W-17283050</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## April 2025

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.15 includes Runtime Manager agent 2.7.2. See
  [Runtime Manager Agent 2.7.2 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-2).

Enterprise Edition License:

- The command `mule -verifyLicenseDetails [path_to_license]` that verifies the license before
  installing it is now added. See
  [Verify or Remove Enterprise Edition License](https://docs.mulesoft.com/on-premises/latest/installing-an-enterprise-license#verify-or-remove-enterprise-edition-license).

### Fixed Issues

Patch release version: 4.6.15

This patch update addresses the following Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p><code>xerces-J</code> is now updated to v2.12.2.</p></div></div></td><td><div><div><p>W-16980865</p></div></div></td></tr><tr><td><div><div><p>Error type in raise-error is now correctly resolved when defined with a static property.</p></div></div></td><td><div><div><p>W-17339304</p></div></div></td></tr><tr><td><div><div><p><code>DuplicateMessageException</code> is now correctly serialized with Kryo.</p></div></div></td><td><div><div><p>W-17844603</p></div></div></td></tr><tr><td><div><div><p>You can now use the <code>mule --verifyLicenseDetails [path-to-license.lic]</code> command to verify a given license file.</p></div></div></td><td><div><div><p>W-17340620</p></div></div></td></tr><tr><td><div><div><p><code>org.apache.cxf:cxf-core</code> is now upgraded to version 3.5.10.</p></div></div></td><td><div><div><p>W-17896358</p></div></div></td></tr></tbody></table>

There is no DataWeave update for this version.

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## March 2025

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.14 includes Runtime Manager agent 2.6.7. See
  [Runtime Manager Agent 2.6.7 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-7).

Feature Flagging Mechanism:

- Mule 4.6 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.6.14

This patch update addresses the following Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Resources are now properly released after a timeout when using the Scatter-Gather or Parallel For Each routers. The <code>mule.forkJoin.completeChildContextsOnTimeout</code> feature flag is now added to enable this behavior.</p></div></div></td><td><div><div><p>W-16941297</p></div></div></td></tr><tr><td><div><div><p><code>MessagingException</code> can now be converted to JSON using DataWeave.</p></div></div></td><td><div><div><p>W-16629236</p></div></div></td></tr><tr><td><div><div><p><code>grizzly-ahc</code> is now upgraded in HTTP Service.</p></div></div></td><td><div><div><p>W-17667949</p></div></div></td></tr><tr><td><div><div><p>Performance degradation no longer occurs when the <code>nonBlockingWriter</code> is enabled for response streaming.</p></div></div></td><td><div><div><p>W-17627284</p></div></div></td></tr><tr><td><div><div><p>A race condition introduced by W-17048606 no longer occurs, where the last part of the response body was truncated when <code>streamResponse</code> flag is set to true in <code>request-connection</code>.</p></div></div></td><td><div><div><p>W-17617940</p></div></div></td></tr><tr><td><div><div><p>Serialization using Object Store V2 with OAuth2 Provider now works as expected.</p></div></div></td><td><div><div><p>W-16673760</p></div></div></td></tr><tr><td><div><div><p>Performance during cache scope execution is now improved.</p></div></div></td><td><div><div><p>W-17671126</p></div></div></td></tr></tbody></table>

DataWeave 2.6.12 is bundled with the Mule 4.6.14 release. This patch release addresses the following
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The Flat File Module now supports YAML files with nested depth greater than 50.</p></div></div></td><td><div><div><p>W-17495145</p></div></div></td></tr><tr><td><div><div><p><code>xerces-j</code> is now updated to 2.12.2.</p></div></div></td><td><div><div><p>W-16918194</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## February 2025

### Patch 4.6.13

The February patch update 4.6.13 addresses a regression in the previous February patch update,
4.6.12, and includes the fixes in the patch.

Patch release version: 4.6.13

This patch update addresses the following Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p><code>ConfigurationException</code> no longer occurs while performing Amazon DynamoDB Connector operations.</p></div></div></td><td><div><div><p>W-17801971</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

### Patch 4.6.12

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.12 includes Runtime Manager agent 2.6.7. See
  [Runtime Manager Agent 2.6.7 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-7).

### Fixed Issues

Patch release version: 4.6.12

This patch update addresses the following Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p><code>InterceptionException</code> is no longer thrown while running MUnit test containing a batch job.</p></div></div></td><td><div><div><p>W-17395302</p></div></div></td></tr><tr><td><div><div><p>The optimization to avoid sending body contents on NTLM type 1 requests added in W-17107281 is now controlled by the feature flag <code>mule.ntlm.avoid.send.payload.on.type1</code>.</p></div></div></td><td><div><div><p>W-17216089</p></div></div></td></tr><tr><td><div><div><p>A <code>ClassCastException</code> thrown when an error occurs within an <code>on-error-continue</code> component no longer prevents transactions from rolling back.</p></div></div></td><td><div><div><p>W-17430963</p></div></div></td></tr><tr><td><div><div><p>A corner case has been fixed and Anypoint Monitoring dashboard now correctly shows all metrics.</p></div></div></td><td><div><div><p>W-16828516</p></div></div></td></tr><tr><td><div><div><p>Kryo serialization issue no longer occurs in Java 17 when running with distributed cluster using authentication, caching policy, and persistent Object Store.</p></div></div></td><td><div><div><p>W-16912085</p></div></div></td></tr><tr><td><div><div><p>Transactions initiated before a <code>flow-ref</code> call are now rolled back in the correct place if an error propagates from the <code>flow-ref</code>.</p></div></div></td><td><div><div><p>W-17453707</p></div></div></td></tr><tr><td><div><div><p>API metrics are now properly sent.</p></div></div></td><td><div><div><p>W-17529530</p></div></div></td></tr></tbody></table>

DataWeave 2.6.11 is bundled with the Mule 4.6.12 release. This patch release addresses the following
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The Java reflection lookup strategy is now improved for bean instances.</p></div></div></td><td><div><div><p>W-17624594</p></div></div></td></tr><tr><td><div><div><p>Compatibility flags created with Mule runtime 4.4 can now be used with older Mule runtime versions.</p></div></div></td><td><div><div><p>W-17372664</p></div></div></td></tr><tr><td><div><div><p>The deconstruct pattern now works as expected when using append on empty objects combined.</p></div></div></td><td><div><div><p>W-16823030</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## January 2025

### Patch 4.6.11

- This patch update reverts the fixes for the following Mule issues: W-17107281 and W-17048606.

- This patch update reverts the fixes for the following DataWeave issues: W-16823030, W-17206423,
  and W-17372664.

### Patch 4.6.10

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.10 includes Runtime Manager agent 2.6.7. See
  [Runtime Manager Agent 2.6.7 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-7).

### Fixed Issues

Patch release version: 4.6.10

This patch update addresses the following Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Windows no longer throws <code>cannot delete file</code> errors during application undeploy.</p></div></div></td><td><div><div><p>W-17050930</p></div></div></td></tr><tr><td><div><div><p><code>BufferOverFlowException</code> with inter-node communication getting stuck no longer occurs when using clusters with encryption under heavy load.</p></div></div></td><td><div><div><p>W-16517561</p></div></div></td></tr><tr><td><div><div><p>Unnecessary internal blocking operations no longer occur when handling large streamed HTTP responses.</p></div></div></td><td><div><div><p>W-17048606</p></div></div></td></tr><tr><td><div><div><p>Body content is no longer sent on Type 1 requests during NTLM authentication.</p></div></div></td><td><div><div><p>W-17107281</p></div></div></td></tr><tr><td><div><div><p>Deploying applications that contain XML SDK connectors no longer causes application class loader memory leak.</p></div></div></td><td><div><div><p>W-16814280</p></div></div></td></tr><tr><td><div><div><p>An infinite loop no longer ocurrs when a redelivery policy is exhausted in a source configured with Transactions and contains an On Error Propagate.</p></div></div></td><td><div><div><p>W-17403761</p></div></div></td></tr><tr><td><div><div><p><code>ConnectionException</code> no longer occurs when using batch processing.</p></div></div></td><td><div><div><p>W-17008722</p></div></div></td></tr><tr><td><div><div><p>A memory leak no longer occurs when using <code>mule-validation-module</code>.</p></div></div></td><td><div><div><p>W-16789548</p></div></div></td></tr><tr><td><div><div><p><code>MessageProcessorNotificationListener</code> is no longer called multiple times when running MUnit suites.</p></div></div></td><td><div><div><p>W-11866494</p></div></div></td></tr><tr><td><div><div><p>A serialization error no longer occurs in Java 17 when using clustering mode or Object Store v2.</p></div></div></td><td><div><div><p>W-17218707</p></div></div></td></tr><tr><td><div><div><p><code>IllegalAccessException</code> is no longer thrown during cache scope serialization with Kryo.</p></div></div></td><td><div><div><p>W-17089503</p></div></div></td></tr><tr><td><div><div><p>All transactions running within a global Error Handler are now committed as expected.</p></div></div></td><td><div><div><p>W-16619771</p></div></div></td></tr></tbody></table>

DataWeave 2.6.10 is bundled with the Mule 4.6.10 release. This patch release addresses the following
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Compatibility flags created with Mule runtime 4.4 can now be used with older Mule runtime versions.</p></div></div></td><td><div><div><p>W-17372664</p></div></div></td></tr><tr><td><div><div><p>The deconstruct pattern now works as expected when using append on empty objects combined.</p></div></div></td><td><div><div><p>W-16823030</p></div></div></td></tr><tr><td><div><div><p>The Java reflection lookup strategy is now improved for bean instances.</p></div></div></td><td><div><div><p>W-17206423</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## November 2024

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.9 includes Runtime Manager agent 2.6.6. See
  [Runtime Manager Agent 2.6.6 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-6).

### Fixed Issues

Patch release version: 4.6.9

This patch update addresses the following Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Memory leak in <code>MuleApplicationClassloader</code> no longer occurs while undeploying an application.</p></div></div></td><td><div><div><p>W-16823349</p></div></div></td></tr><tr><td><div><div><p>A batch serialization error no longer occurs in Java 17 when one of the steps throws <code>SQLException</code>.</p></div></div></td><td><div><div><p>W-16546951</p></div></div></td></tr><tr><td><div><div><p>A deadlock no longer occurs when consuming the payload in the completion callback of the HTTP client <code>sendAsync</code> method.</p></div></div></td><td><div><div><p>W-16640190</p></div></div></td></tr><tr><td><div><div><p><code>NullPointerException</code> no longer occurs when undeploying an application with native libraries in Windows OS.</p></div></div></td><td><div><div><p>W-16712841</p></div></div></td></tr><tr><td><div><div><p>Log4j2 monorepo is upgraded to 2.24.1.</p></div></div></td><td><div><div><p>W-16889265</p></div></div></td></tr><tr><td><div><div><p>The <code>commons-io:commons-io</code> dependency is upgraded to 2.17.0.</p></div></div></td><td><div><div><p>W-16843119</p></div></div></td></tr></tbody></table>

DataWeave 2.6.9 is bundled with the Mule 4.6.9 release. This patch release addresses the following
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The <code>stripTrailingZeroes</code> compatibility flag is now added to preserve the decimal format.</p></div></div></td><td><div><div><p>W-17030593</p></div></div></td></tr><tr><td><div><div><p>Apache POI folder used for temporal files is no longer deleted.</p></div></div></td><td><div><div><p>W-16899674</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## October 2024

### What’s New

Runtime Manager agent:

- This release of Mule runtime 4.6.8 includes Runtime Manager agent 2.6.6. See
  [Runtime Manager Agent 2.6.6 Release Notes](https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agent-2.6.x-release-notes#2-6-6).

### Fixed Issues

Patch release version: 4.6.8

This patch update addresses the following Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Spring Core is upgraded to 5.3.39.</p></div></div></td><td><div><div><p>W-16519084</p></div></div></td></tr><tr><td><div><div><p>The <code>configuration-properties</code> encoding parameter is no longer ignored.</p></div></div></td><td><div><div><p>W-12228892</p></div></div></td></tr><tr><td><div><div><p>Web Service Consumer Connector and RosettaNet Connector no longer fails when there is an HTTP TLS transport configuration.</p></div></div></td><td><div><div><p>W-16288302</p></div></div></td></tr><tr><td><div><div><p><code>InitialisationException</code> is no longer thrown when using the Raise Error component with an extra space at the end of the type field.</p></div></div></td><td><div><div><p>W-16237424</p></div></div></td></tr><tr><td><div><div><p>Kryo serialization now works as expected with <code>ResourceOwnerOAuthContextWithRefreshState</code> when using Java 17.</p></div></div></td><td><div><div><p>W-16533466</p></div></div></td></tr><tr><td><div><div><p>Kryo serialization now works as expected when executing the Rate Limit policy in Java17.</p></div></div></td><td><div><div><p>W-16843706</p></div></div></td></tr><tr><td><div><div><p>Fatal errors no longer occur when loading native libraries in Java 17.</p></div></div></td><td><div><div><p>W-16787783</p></div></div></td></tr><tr><td><div><div><p><code>java.lang.InstantiationError : java.util.Map</code> is no longer thrown when applying an authentication policy.</p></div></div></td><td><div><div><p>W-16595277</p></div></div></td></tr><tr><td><div><div><p>When the feature flag <code>anypoint.platform.keep.default.policy.format</code> is set to <code>true</code> or the policy minimum Mule version is 4.5.0, the policy name format is now <code>${policyName} @ ${artifactName} - ${flowName}</code>.</p></div></div></td><td><div><div><p>W-16169887</p></div></div></td></tr><tr><td><div><div><p>Logging for the Analytics <code>.db</code> files cleanup is now improved.</p></div></div></td><td><div><div><p>W-16624763</p></div></div></td></tr><tr><td><div><div><p><code>grizzly-ahc</code> is now upgraded in the HTTP service.</p></div></div></td><td><div><div><p>W-16734361</p></div></div></td></tr><tr><td><div><div><p>Race condition now causes an infinite loop in Grizzly AHC.</p></div></div></td><td><div><div><p>W-16599945</p></div></div></td></tr></tbody></table>

DataWeave 2.6.8 is bundled with the Mule 4.6.8 release. This patch release addresses the following
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>DataWeave descendant selector performance is now improved.</p></div></div></td><td><div><div><p>W-16343577</p></div></div></td></tr><tr><td><div><div><p>Streaming capability for arguments at <code>sum</code>, <code>countBy</code>, and <code>sumBy</code> functions is now enabled.</p></div></div></td><td><div><div><p>W-16125755</p></div></div></td></tr><tr><td><div><div><p>Input/output <code>MimeType</code> properties are now preserved as expected.</p></div></div></td><td><div><div><p>W-16161736</p></div></div></td></tr><tr><td><div><div><p>Access error for Java 17 encapsulation errors is now improved.</p></div></div></td><td><div><div><p>W-15705596</p></div></div></td></tr><tr><td><div><div><p>Coercion error is now caught inside <code>try</code> as expected.</p></div></div></td><td><div><div><p>W-15323897</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## September 2024

### What’s New

- `cxfVersion` is upgraded to 3.5.9.

- JaCoCo is upgraded to 0.8.11.

- Maven JAR Plugin is upgraded to 3.3.0.

### Fixed Issues

Patch release version: 4.6.7

This patch update addresses the following Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p><code>NullPointerException</code> is no longer thrown when DataWeave transforms a <code>RetryPolicyExhaustedException</code> to a JSON format on a Java 17 runtime.</p></div></div></td><td><div><div><p>W-15643200</p></div></div></td></tr><tr><td><div><div><p>Properties files are now located in the <code>lib/user</code> directory during application deployment.</p></div></div></td><td><div><div><p>W-16404468</p></div></div></td></tr><tr><td><div><div><p><code>com.google.gson.stream.MalformedJsonException</code> is no longer thrown while deploying an application.</p></div></div></td><td><div><div><p>W-16343071</p></div></div></td></tr><tr><td><div><div><p>Debug logs for custom policies containing a custom extension/connector now work correctly.</p></div></div></td><td><div><div><p>W-15286605</p></div></div></td></tr><tr><td><div><div><p>The process of unloading native libraries in Windows OS running on Java 8 and Java 11 is now improved.</p></div></div></td><td><div><div><p>W-16375439</p></div></div></td></tr><tr><td><div><div><p><code>cxfVersion</code> is upgraded to 3.5.9.</p></div></div></td><td><div><div><p>W-16436783</p></div></div></td></tr><tr><td><div><div><p>JaCoCo is upgraded to 0.8.11.</p></div></div></td><td><div><div><p>W-14866639</p></div></div></td></tr><tr><td><div><div><p><code>maven-jar-plugin</code> is upgraded to 3.3.0.</p></div></div></td><td><div><div><p>W-14580541</p></div></div></td></tr><tr><td><div><div><p>Policies with minimum Mule version 4.4.0 now use the flow name as part of the artifact name, when the feature flag <code>anypoint.platform.keep.default.policy.format=true</code> is set.</p></div></div></td><td><div><div><p>W-16169887</p></div></div></td></tr><tr><td><div><div><p><code>NullPointerException</code> is no longer thrown when API Gateway tries to dispose an empty cluster.</p></div></div></td><td><div><div><p>W-16540685</p></div></div></td></tr><tr><td><div><div><p>API Gateway pollers are no longer initialized when the API Gateway is started in offline mode.</p></div></div></td><td><div><div><p>W-16093885</p></div></div></td></tr><tr><td><div><div><p>Race condition no longer causes byte buffer disposal errors when deploying policies.</p></div></div></td><td><div><div><p>W-16450677</p></div></div></td></tr></tbody></table>

DataWeave 2.6.7 is bundled with the Mule 4.6.7 release. This patch release addresses the following
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>DataWeave now preserves MimeType properties correctly.</p></div></div></td><td><div><div><p>W-16161736</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## August 2024

Patch release version: 4.6.6

This patch update addresses the following Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Loaded native libraries are now copied into a separate temporary folder to avoid issues while redeploying applications in Windows OS.</p></div></div></td><td><div><div><p>W-15894519</p></div></div></td></tr><tr><td><div><div><p>Parameter resolution error handling is no longer affected when the parameterized operation is inside a dynamically referenced subflow.</p></div></div></td><td><div><div><p>W-15923581</p></div></div></td></tr><tr><td><div><div><p>The OAuth token invalidation status is now communicated to other nodes in a cluster when a token is invalidated on one node.</p></div></div></td><td><div><div><p>W-15154658</p></div></div></td></tr><tr><td><div><div><p>Flows now honour the state configured in <code>flows.deployment.properties</code> when restarting the app, regardless of the initial state. To enable this feature, use the <code>mule.honour.persisted.flow.state</code> system property. This only applies to Standalone and Hybrid deployments.</p></div></div></td><td><div><div><p>W-15750334</p></div></div></td></tr><tr><td><div><div><p>Mule runtime startup no longer fails when <code>MULE_HOME</code> has a blank space on Windows OS.</p></div></div></td><td><div><div><p>W-15346051</p></div></div></td></tr><tr><td><div><div><p>A serialization exception is no longer thrown when a Batch Step fails with a <code>ModuleException</code> in Java 17.</p></div></div></td><td><div><div><p>W-15808825</p></div></div></td></tr><tr><td><div><div><p><code>mule-script-module</code> is now improved to ensure that beans no longer contain invalid references to injected dependencies, whether they are directly or indirectly reliant on MuleConfiguration.</p></div></div></td><td><div><div><p>W-15832941</p></div></div></td></tr><tr><td><div><div><p>Jars in <code>lib/user</code> are now visible from jars in <code>lib/opt</code>. For example, using cluster persistence with the JDBC driver provided in <code>lib/user</code> no longer fails with a <code>Could not load driverClass error</code>.</p></div></div></td><td><div><div><p>W-16010357</p></div></div></td></tr><tr><td><div><div><p>Serialization now works as expected with Batch Job and Salesforce BulkOperationResult in Java 17.</p></div></div></td><td><div><div><p>W-16105403</p></div></div></td></tr><tr><td><div><div><p>Batch module no longer fails with a <code>Could not serialize object</code> error when client ID enforcement policy is enabled.</p></div></div></td><td><div><div><p>W-16124318</p></div></div></td></tr><tr><td><div><div><p>Deploying a policy no longer fails while using a mule directory with whitespaces.</p></div></div></td><td><div><div><p>W-15440100</p></div></div></td></tr><tr><td><div><div><p><code>ClassNotFoundException</code> is no longer thrown when upgrading from Mule runtime 4.4.0 using the OAuth 2 authentication code and Object Store V2 stored tokens.</p></div></div></td><td><div><div><p>W-15595791</p></div></div></td></tr><tr><td><div><div><p><code>NullPointerException</code> no longer occurs when having MQ connector as a dependency in MUnit 3.1.0.</p></div></div></td><td><div><div><p>W-15734679</p></div></div></td></tr><tr><td><div><div><p>API Gateway initialization no longer fails if quorum isn’t reached in cluster mode.</p></div></div></td><td><div><div><p>W-15951155</p></div></div></td></tr><tr><td><div><div><p>Hard timeout for platform requests is now available by setting up the <code>anypoint.platform.request_timeout</code> in milliseconds.</p></div></div></td><td><div><div><p>W-16141554</p></div></div></td></tr></tbody></table>

DataWeave 2.6.6 is bundled with the Mule 4.6.6 release. This patch release addresses the following
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Argument materialization is now improved at the <code>dw::Runtime::try</code> function.</p></div></div></td><td><div><div><p>W-15323897</p></div></div></td></tr><tr><td><div><div><p>Streaming capability is now enabled for arguments of <code>sum</code>, <code>countBy</code>, and <code>sumBy</code> functions.</p></div></div></td><td><div><div><p>W-16125755</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## July 2024

Patch release version: 4.6.5

This patch update addresses the following Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>The <code>mule-assembly-content-descriptor</code> file size no longer differs between <code>mule-ee-distribution-standalone</code> ZIP and Tar GZ distributions.</p></div></div></td><td><div><div><p>W-15397610</p></div></div></td></tr><tr><td><div><div><p>The redeployment of an app with a domain using a Groovy component no longer throws the <code>groovy.lang.MissingMethodException</code> exception.</p></div></div></td><td><div><div><p>W-15750766</p></div></div></td></tr><tr><td><div><div><p>Batch job instance queue store files are removed after completion.</p></div></div></td><td><div><div><p>W-15546969</p></div></div></td></tr><tr><td><div><div><p>Cache scope with multiple computations no longer occurs if events arrive concurrently for an absent key.</p></div></div></td><td><div><div><p>W-14604517</p></div></div></td></tr><tr><td><div><div><p>Tanuki wrapper configuration is now enabled for AArch64.</p></div></div></td><td><div><div><p>W-15839796</p></div></div></td></tr><tr><td><div><div><p>MDC context is reset after the XML SDK operation is executed.</p></div></div></td><td><div><div><p>W-15206528</p></div></div></td></tr><tr><td><div><div><p>MUnit tests no longer fail with <code>groupId cannot be null</code> when using a parent POM for dependencies and plugins.</p></div></div></td><td><div><div><p>W-14998254</p></div></div></td></tr><tr><td><div><div><p>Maven plugin versions are updated to be compatible with Maven 3.9.</p></div></div></td><td><div><div><p>W-15554914</p></div></div></td></tr><tr><td><div><div><p>JRuby dependency is upgraded to 9.4.7.0.</p></div></div></td><td><div><div><p>W-15757000</p></div></div></td></tr><tr><td><div><div><p>Deploying a policy in Windows no longer fails in folders containing whitespaces.</p></div></div></td><td><div><div><p>W-16112611</p></div></div></td></tr><tr><td><div><div><p>Open Telemetry tracing support is now added to policies.</p></div></div></td><td><div><div><p>W-15633203</p></div></div></td></tr><tr><td><div><div><p>Kerberos is now enabled for proxy authentication against Anypoint Platform for Gateway capabilities.</p></div></div></td><td><div><div><p>W-15642605</p></div></div></td></tr><tr><td><div><div><p>Default stronger validations for policies are now added after applying the property <code>anypoint.platform.validate_policy_schemas</code>.</p></div></div></td><td><div><div><p>W-15769926</p></div></div></td></tr><tr><td><div><div><p>Logging for Gateway Analytics initialization is now improved.</p></div></div></td><td><div><div><p>W-15904845</p></div></div></td></tr><tr><td><div><div><p>Handling of connection errors with API platform is now improved.</p></div></div></td><td><div><div><p>W-15809377</p></div></div></td></tr><tr><td><div><div><p>Default gatekeeping for APIs that fail when doing a rollback is now added using the property <code>anypoint.platform.gatekeeper.block_failed_revert</code>.</p></div></div></td><td><div><div><p>W-15427352</p></div></div></td></tr></tbody></table>

DataWeave 2.6.5 is bundled with the Mule 4.6.5 release. This patch release addresses the following
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Enforced Java accessibility restrictions only for Mule apps with DataWeave language level version 2.6 and later and executing with Java 17 and later.</p></div></div></td><td><div><div><p>W-15832793</p></div></div></td></tr><tr><td><div><div><p>Materialization issues no longer occur with schema properties.</p></div></div></td><td><div><div><p>W-15839190</p></div></div></td></tr><tr><td><div><div><p>The Flat File module now adds the <code>substituteCharacterAsMissingValue</code> reader property.</p></div></div></td><td><div><div><p>W-15571377</p></div></div></td></tr><tr><td><div><div><p>The Flat File module now adds the <code>fillRedefinesByMaxLength</code> writer property.</p></div></div></td><td><div><div><p>W-15973636</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## June 2024

Patch release version: 4.6.4

This patch update addresses the following Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Applications configured with OAuth and running on Java 17 are now correctly serialized.</p></div></div></td><td><div><div><p>W-15425364</p></div></div></td></tr><tr><td><div><div><p>You can now see the number of flows considered for UBP and what those flows are when the application starts.</p></div></div></td><td><div><div><p>W-14401338</p></div></div></td></tr><tr><td><div><div><p><code>plexus-archiver</code> is upgraded to 4.9.1.</p></div></div></td><td><div><div><p>W-14821825</p></div></div></td></tr><tr><td><div><div><p>The version in the <code>pom.xml</code> file is now parsed when containing the property <code>${text}</code>.</p></div></div></td><td><div><div><p>W-15228973</p></div></div></td></tr><tr><td><div><div><p>Events with statistics are now correctly serialized for applications running on Java 17.</p></div></div></td><td><div><div><p>W-15542604</p></div></div></td></tr><tr><td><div><div><p>The exception <code>java.lang.IllegalAccessException</code> no longer occurs when using <code>itemSequenceInfo</code> in DataWeave.</p></div></div></td><td><div><div><p>W-15617764</p></div></div></td></tr><tr><td><div><div><p>DataWeave compiled expressions cache is no longer overpopulated when using nested templates.</p></div></div></td><td><div><div><p>W-15782010</p></div></div></td></tr><tr><td><div><div><p>Batch job serialization now works as expected when running on Java 17.</p></div></div></td><td><div><div><p>W-15345812</p></div></div></td></tr><tr><td><div><div><p>Tracing variables inside XML operations are no longer propagated to the flows.</p></div></div></td><td><div><div><p>W-15206528</p></div></div></td></tr><tr><td><div><div><p><code>jackson-databind</code> is upgraded to 2.15.4.</p></div></div></td><td><div><div><p>W-15628361</p></div></div></td></tr><tr><td><div><div><p><code>NullPointerException</code> no longer occurs on AST-deserialized applications using Anypoint Custom Metrics Connector.</p></div></div></td><td><div><div><p>W-15677894</p></div></div></td></tr><tr><td><div><div><p>Resiliency is now improved on policy application and updates.</p></div></div></td><td><div><div><p>W-15426519</p></div></div></td></tr></tbody></table>

DataWeave 2.6.4 is bundled with the Mule 4.6.4 release. This patch release addresses the following
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>A <code>java.io.IOException</code> exception no longer occurs when writing the same binary input multiple times for JSON and XML formats.</p></div></div></td><td><div><div><p>W-14589732</p></div></div></td></tr><tr><td><div><div><p>The Excel writer now generates XLSX files using ZIP specification 2.0.</p></div></div></td><td><div><div><p>W-15534640</p></div></div></td></tr><tr><td><div><div><p>When comparing a <code>Date</code> with a <code>String</code> representation of a date, the <code>Date</code> format is now used to coerce the <code>String</code> accordingly.</p></div></div></td><td><div><div><p>W-15478713</p></div></div></td></tr><tr><td><div><div><p>Access error messages for Java 17 encapsulation errors are now improved.</p></div></div></td><td><div><div><p>W-15705596</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## May 2024

Patch release version: 4.6.3

This patch update addresses the following Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Client, policy, and API names are now shown when logging Analytics events.</p></div></div></td><td><div><div><p>W-15294568</p></div></div></td></tr><tr><td><div><div><p>When upgrading a policy, templates are now downloaded before the previous version is removed.</p></div></div></td><td><div><div><p>W-15212679</p></div></div></td></tr><tr><td><div><div><p>When applying a policy that initially failed but was later applied successfully, the retry initiated by the gateway no longer causes an exception error.</p></div></div></td><td><div><div><p>W-15186491</p></div></div></td></tr><tr><td><div><div><p>Joda-Time is upgraded to v2.12.7.</p></div></div></td><td><div><div><p>W-15511864</p></div></div></td></tr><tr><td><div><div><p>Apache CXF is upgraded to version 3.5.8.</p></div></div></td><td><div><div><p>W-15293232</p></div></div></td></tr><tr><td><div><div><p>Getting metadata from a XSD with <code>vc:minVersion=1.1</code> no longer causes a <code>NullPointerException</code> error.</p></div></div></td><td><div><div><p>W-15193303</p></div></div></td></tr></tbody></table>

DataWeave 2.6.3 is bundled with the Mule 4.6.3 release. This patch release addresses the following
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p><code>ArithmeticException</code> no longer executes <code>toHex</code> with non-integer numbers.</p></div></div></td><td><div><div><p>W-15006840</p></div></div></td></tr><tr><td><div><div><p>Performance degradation no longer occurs when an array is concatenated.</p></div></div></td><td><div><div><p>W-15399854</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## April 2024

Patch release version: 4.6.2

This patch update addresses the following Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p><code>NullPointerException</code> no longer occurs when deploying domains.</p></div></div></td><td><div><div><p>W-15159880</p></div></div></td></tr><tr><td><div><div><p>Hazelcast is upgraded to 5.2.5.</p></div></div></td><td><div><div><p>W-15274674</p></div></div></td></tr><tr><td><div><div><p>Spring is upgraded to 5.3.33.</p></div></div></td><td><div><div><p>W-15260752</p></div></div></td></tr><tr><td><div><div><p>GraalJS is upgraded to 22.3.5.</p></div></div></td><td><div><div><p>W-15284493</p></div></div></td></tr><tr><td><div><div><p>MUnit tests using tracing module and "Set logging variable" now work as expected.</p></div></div></td><td><div><div><p>W-14773408</p></div></div></td></tr><tr><td><div><div><p>Using <code>vc:minVersion="1.1"</code> in XSD schema no longer throws <code>NullPointerException</code> in XML SDK connectors.</p></div></div></td><td><div><div><p>W-15081363</p></div></div></td></tr><tr><td><div><div><p>Template parser validation is now improved.</p></div></div></td><td><div><div><p>W-15141905</p></div></div></td></tr></tbody></table>

DataWeave 2.6.2 is bundled with the Mule 4.6.2 release. This patch release addresses the following
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Inconsistent behavior no longer occurs between in-memory and streaming XML parsers for deciding document encoding.</p></div></div></td><td><div><div><p>W-15110015</p></div></div></td></tr><tr><td><div><div><p>Streaming for DataWeave-based data formats like <code>ndjson</code> now works as expected.</p></div></div></td><td><div><div><p>W-15262860</p></div></div></td></tr><tr><td><div><div><p>The Excel reader no longer reads furigana characters.</p></div></div></td><td><div><div><p>W-14991276</p></div></div></td></tr><tr><td><div><div><p>Coercion of the third parameter on the ternary function executor now works as expected.</p></div></div></td><td><div><div><p>W-15061008</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## March 2024

Patch release version: 4.6.1

This patch update addresses the following Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Performance is now improved for certain For Each scenarios.</p></div></div></td><td><div><div><p>W-14678431</p></div></div></td></tr><tr><td><div><div><p>HTTP Request Connector no longer throws <code>Connection limit exceeded, cannot process request</code> when <code>maxConnections</code> is set to 1.</p></div></div></td><td><div><div><p>W-14686211</p></div></div></td></tr><tr><td><div><div><p>Disabling the <code>enableNotifications</code> flag on the On Error Continue component now works as expected.</p></div></div></td><td><div><div><p>W-14954677</p></div></div></td></tr><tr><td><div><div><p>Multi-step batch jobs can now be correctly resumed and finished after being stopped.</p></div></div></td><td><div><div><p>W-14726677</p></div></div></td></tr><tr><td><div><div><p>The error message is now improved for exceptions that occur when loading an extension because of Java version incompatibility.</p></div></div></td><td><div><div><p>W-14934626</p></div></div></td></tr><tr><td><div><div><p>The error message <code>namespace already exists</code> is no longer thrown when using the same namespace with the current module or extension namespace for apps using the XML SDK component.</p></div></div></td><td><div><div><p>W-14559071</p></div></div></td></tr><tr><td><div><div><p>Transactions' timeout is now honored. When a transaction times out, it is rolled back, and an error is thrown that can be handled with error handling. To enable this, activate the <code>mule.tx.error.when.timeout</code> feature flag.</p></div></div></td><td><div><div><p>W-14128870</p></div></div></td></tr><tr><td><div><div><p>Memory leaks no longer occur when using the <code>mule-scripting-module</code> dependency with HTTP Connector.</p></div></div></td><td><div><div><p>W-14479158</p></div></div></td></tr><tr><td><div><div><p>Java JDK <code>inlineDeclaration</code> now resolves correctly for stateless subtypes.</p></div></div></td><td><div><div><p>W-14645134</p></div></div></td></tr></tbody></table>

DataWeave 2.6.1 is bundled with the Mule 4.6.1 release. This patch release addresses the following
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Performance is now improved when coercing addition and subtraction operations.</p></div></div></td><td><div><div><p>W-14927555</p></div></div></td></tr></tbody></table>

For guidance with the patching process, see
[Apply Patch Updates](https://docs.mulesoft.com/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates).

## February 6, 2024

### What’s New

The 4.6.0 version of Mule runtime introduces the following enhancements:

Java adoption:

- MuleSoft is adopting Java’s long-term support (LTS) release cadence, beginning with Mule runtime
  4.6, which adds support for Java 17 LTS. See [Java Adoption](https://docs.mulesoft.com/release-notes/mule-runtime/java-adoption).

  > [!NOTE] The maximum supported version for running your applications is Java 17 for Mule runtime
  > 4.6.x and later. During the packaging of your app, all code, including third-party dependencies,
  > **must** be compiled for Java 8.

- Java 17 manages memory differently than Java 8. See
  [Application Performance](https://docs.mulesoft.com/general/java-support#application-performance).

- Mule runtime classes are now modularized per the Java module system introduced back in Java 9
  (also known as JPMS or Project Jigsaw). Reflective introspection of Mule runtime classes is now
  limited. To maintain backward compatibility, reflective access to classes defined within the scope
  of your applications and domains remains open to access.

- Java EE libraries are now removed from Mule runtime for Java 17.

Mule Gateway improvements:

- You can now upgrade your policies and API proxies to Java 17. See
  [Upgrading Policies](https://docs.mulesoft.com/general/java-support#policies) and
  [Upgrading API Proxies](https://docs.mulesoft.com/general/java-support#api-proxies).

- Mule Gateway now supports API analytics event logging. To enable event logging, see
  [Log Analytics Event Data](https://docs.mulesoft.com/mule-gateway/mule-gateway-metrics#log-analytics-event-data).

- Mule Gateway now supports automatically deleting cached policy files. To enable this feature, see
  [Cached Policy Assets Deletion](https://docs.mulesoft.com/mule-gateway/policies-policy-overview#cached-policy-assets-deletion).

Mule SDK improvements:

- Mule SDK (Java SDK and XML SDK) now support Java 17. See
  [Upgrading Custom Connectors](https://docs.mulesoft.com/general/java-support#custom-connectors).

- Java SDK now includes the new `@JavaVersionSupport` annotation. See
  [Supported Java Version Concept](https://docs.mulesoft.com/general/customer-connector-upgrade#release-your-custom-connector).

- XML SDK now supports TLS. See [XML SDK TLS Support](https://docs.mulesoft.com/mule-sdk/latest/xml-sdk#xml-sdk-tls).

General improvements:

- The Joda-Time library is upgraded to version 2.12.5.

- The GraalJS library is upgraded to 22.3.3.

### DataWeave Features

The 2.6.0 version of DataWeave introduces these new features and enhancements:

Extended format support:

- DataWeave now supports Java 17. See [Java Format](https://docs.mulesoft.com/dataweave/latest/dataweave-formats-java).

- Mule expression language service are now modularized.

### Fixed Issues

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

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p><code>aspectj</code> is now removed from distribution.</p></div></div></td><td><div><div><p>W-13913357</p></div></div></td></tr><tr><td><div><div><p>The Joda-Time library is upgraded to version 2.12.5.</p></div></div></td><td><div><div><p>W-13913362</p></div></div></td></tr><tr><td><div><div><p>The GraalJS library is upgraded to 22.3.3.</p></div></div></td><td><div><div><p>W-13961780</p></div></div></td></tr><tr><td><div><div><p>MUnit no longer fails with apps using Anypoint Connector for DotNet (DotNet Connector).</p></div></div></td><td><div><div><p>W-14747448</p></div></div></td></tr><tr><td><div><div><p><code>NullPointerException</code> no longer occurs in XSD parsing when a schema has a <code>minVersion</code>/<code>maxVersion</code>.</p></div></div></td><td><div><div><p>W-14748090</p></div></div></td></tr><tr><td><div><div><p>Timeout is not considered for local transactions and rollbacks are silently executed.</p></div></div></td><td><div><div><p>W-14608096</p></div></div></td></tr><tr><td><div><div><p>MediaType cache now has a maximum size to prevent leaks.</p></div></div></td><td><div><div><p>W-14490182</p></div></div></td></tr><tr><td><div><div><p>DataWeave now uses objects as part of the Mule API.</p></div></div></td><td><div><div><p>W-14185880</p></div></div></td></tr><tr><td><div><div><p>License installation no longer fails with <code>FileNotFoundException</code>.</p></div></div></td><td><div><div><p>W-14542349</p></div></div></td></tr><tr><td><div><div><p>Legacy properties builder no longer reevaluates from root resolver placeholders.</p></div></div></td><td><div><div><p>W-14616618</p></div></div></td></tr><tr><td><div><div><p><code>JAVA_HOME</code> is now properly handled by Surefire.</p></div></div></td><td><div><div><p>W-12082402</p></div></div></td></tr><tr><td><div><div><p>HTTP Redirect no longer works on Mule runtime 4.x on HTTP Post.</p></div></div></td><td><div><div><p>W-14619216</p></div></div></td></tr><tr><td><div><div><p>Race condition no longer results in <code>NullPointerException</code> when the Write Queue is full.</p></div></div></td><td><div><div><p>W-14543363</p></div></div></td></tr><tr><td><div><div><p>Container of the Embedded Runtime no longer stops if it wasn’t created.</p></div></div></td><td><div><div><p>W-14321634</p></div></div></td></tr><tr><td><div><div><p>Unnecessary MBeans for JMX management are no longer registered.</p></div></div></td><td><div><div><p>W-12422473</p></div></div></td></tr><tr><td><div><div><p>Internal dependency graph is now generated only once for all validations.</p></div></div></td><td><div><div><p>W-12421187</p></div></div></td></tr><tr><td><div><div><p>Extension model parsing no longer fails for extensions with dependencies declared as <code>provided</code>.</p></div></div></td><td><div><div><p>W-14646484</p></div></div></td></tr></tbody></table>

DataWeave 2.6.0 is bundled with the Mule 4.6.0 release. This release addresses the following
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Caching now works correctly when coercing for addition and subtraction operations.</p></div></div></td><td><div><div><p>W-14591653</p></div></div></td></tr><tr><td><div><div><p><code>do</code> scope declarations with pattern matching now properly reflect variable names when variables are optimized with common subexpression elimination.</p></div></div></td><td><div><div><p>W-14514837</p></div></div></td></tr><tr><td><div><div><p>The <code>minInflateRatio</code> property is now added to Excel format to control the zip bomb check threshold.</p></div></div></td><td><div><div><p>W-14315728</p></div></div></td></tr></tbody></table>

### Bundled Components

- DataWeave version 2.6.0

- Runtime Manager Agent plugin version 2.6.0

### Upgrade

If you are upgrading to this version of Mule from an earlier Mule 4.x version, see
[Mule Upgrades and Patch Updates](https://docs.mulesoft.com/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:

<table><colgroup><col> <col></colgroup><thead><tr><th>Module or Extension</th><th>Version</th></tr></thead><tbody><tr><td><p>APIkit for Mule 4</p></td><td><p>1.10.1</p></td></tr><tr><td><p>APIkit for OData</p></td><td><p>2.2.1</p></td></tr><tr><td><p>APIkit for OData 4</p></td><td><p>1.3.4</p></td></tr><tr><td><p>APIkit for SOAP</p></td><td><p>1.4.1</p></td></tr><tr><td><p>APIkit for GraphQL</p></td><td><p>1.0.0</p></td></tr><tr><td><p>Spring module</p></td><td><p>1.3.11</p></td></tr><tr><td><p>MUnit plugin</p></td><td><p>3.1.0</p></td></tr></tbody></table>

### 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

- [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.6/mule-troubleshooting-plugin)

- [Known Issues](https://help.salesforce.com/s/issues)