--- schema_version: "1" id: 20537e3959a765b3afa54156177a834a145c8a97a7111b41d5d5a6b88a062187 title: Mule Runtime Engine 4.6.0 Release Notes collection: mulesoft version: current locale: ja-jp portal_url: https://docs.salesforce.com/mulesoft/current/ja-jp/release-notes/mule-runtime/mule-4.6.0-release-notes.md canonical_url: https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.6.0-release-notes source_site: docs.mulesoft.com content_type: documentation content_hash: c2a8383bc66c62059fd7914a04ab10c6de9620faae11d8579394baddb009165c description: MuleSoft Documentation Site latest: true --- # Mule Runtime Engine 4.6.0 Release Notes Mule runtime engine (Mule) is a lightweight integration engine that runs Mule applications and supports domains and policies. This version of Mule provides important enhancements and fixes. Deploy all your new and existing applications to the latest version to benefit from the improvements. ## [](#october-2026)October 2026 ### Fixed Issues ### [](#patch-4-6-36)Patch 4.6.36 The October patch update 4.6.36 addresses regressions in the October patch update 4.6.35.
Issue Resolution ID

Mule

SLA-based rate limiting policies no longer reject valid client requests because the client is validated twice.

W-24447995
### [](#patch-4-6-35)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/jp/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:
Issue Resolution ID

The Reactor Core library is upgraded to 3.8.7.

W-3300013

The Jackson library is upgraded to 2.22.2.

W-23947149

The jsoup library is upgraded to 1.23.2.

W-23987949

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 mule.properties.resolution.maxDepth system property, which defaults to 10.

W-23650198

Error-mapping preservation during error propagation can now be enabled through the mule.honourErrorMappingsOnErrorPropagation 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.

W-23955755

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.

W-24234538

Network information listening ports are now scoped to the Mule process.

W-24043880

NullPointerException errors no longer occur when loading the extension model of a connector whose connection provider uses the @ClientCredentials or @AuthorizationCode OAuth annotation with credentialsPlacement configured.

W-24086656

Policy logging context is no longer lost when a dynamic Flow Reference resolves to a subflow.

W-24026465

The new loggingConfiguration troubleshooting operation helps you diagnose logging configuration issues.

W-23998256

The log level for disallowConcurrentExecution messages is changed from WARN to DEBUG, reducing log noise.

W-24164028

The new on-demand connectivity-testing troubleshooting operation is now available.

W-23629284

An SDK API for queues (VM usage) and core adapters is added.

W-19439432

The new on-demand connectionCount troubleshooting operation is now available.

W-23716301

A warning is now logged when NTLM authentication is configured but the server doesn’t issue an NTLM challenge.

W-17651806

Fallback is now enabled as the default strategy for contracts collection. To change the behavior, configure the anypoint.platform.clients_fetch_mode system property with the values sharded, legacy, or fallback.

W-24179706

When API Gateway authenticates with Anypoint Platform, a transient failure of the /login request no longer discards an otherwise valid Access Management token. The token is now invalidated only on an actual authentication failure (401 or 403).

W-24144244
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#september-2026)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/jp/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:
Issue Resolution ID

An <async> 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 mule.async.gracefulShutdown.drainInflight system property.

W-23602447

An SDK-based reconnectable message source no longer attempts to reconnect while a graceful shutdown is in progress.

W-23122573

Custom error mappings in the Tracing module are no longer lost on error propagation when an operation inside a tracing:with-correlation-id scope fails, which previously reverted the mapped error type to the raw connector error.

W-21815402

A memory leak no longer occurs when parallel-foreach and scatter-gather routes leave the route event pinned in a worker thread’s memory after route completion.

W-23829061

Artifact descriptor validation failures during deployment now report more specific exceptions.

W-23047228

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 anypoint.platform.error.mapping (format NAMESPACE:IDENTIFIER:STATUS_CODE, comma-separated for multiple mappings) and anypoint.platform.error.default system properties.

W-23509148

API Gateway no longer fails to read shard checksums from an ETag header that contains commas.

W-23572494

The fix for idle connections being destroyed and recreated instead of reused when the number of idle connections reached the configured maxIdle limit under concurrent load, introduced in a previous release, is reverted in this release.

W-22716456

The jsoup library is upgraded to 1.23.1.

W-23715606

The Apache Commons Compress library is upgraded to 1.26.0.

W-3300013

The Jackson library is upgraded to 2.22.1.

W-23540335

The RAML Parser library is upgraded to 2-1.2.1.

W-23328350

The com.mulesoft.mule.runtime.gw.api.analytics package is now open to all modules, so the Runtime Manager agent can serialize analytics events.

W-23846531
DataWeave 2.6.30 is bundled with the Mule 4.6.34 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

You can now configure the size of the DataWeave script parser cache by using the mule.weave.script.parser.cache.size system property.

W-23138851

A thread-safety livelock no longer occurs in the Java module builder and converter caches.

W-23652160
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#august-2026)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/jp/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:
Issue Resolution ID

Idle connections are no longer destroyed and recreated instead of being reused when the number of idle connections reaches the configured maxIdle limit under concurrent load.

W-22716456

A batch job no longer fails with a MULE:CANCELLED error during graceful shutdown.

W-23426859

Potential errors thrown during runtime shutdown are now handled correctly.

W-23051939

The Diagnostic Information Analysis File (DIAF) now includes network information.

W-22383655

The Diagnostic Information Analysis File (DIAF) now includes Mule agent information.

W-22383660

The Diagnostic Information Analysis File (DIAF) now includes a platform connectivity check.

W-22383679

The API gateway resource cache is enabled by default. You can now disable it by setting the anypoint.platform.resource_cache_enabled system property to false.

W-23542185

The Jackson library is upgraded to 2.22.0.

W-23121654
DataWeave 2.6.29 is bundled with the Mule 4.6.33 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

The repeated attribute selector (.*@) now correctly preserves values when processing data structures containing empty map slots.

W-23457314

The Jackson library is upgraded to 2.21.5.

W-23037592
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#july-2026)July 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.32 includes Runtime Manager agent 2.7.16. See [Runtime Manager Agent 2.7.16 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-16). Feature Flagging Mechanism: - Mule 4.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:
Issue Resolution ID

A NullPointerException error no longer occurs in event context handling when a flow times out while a non-blocking operation is still in flight.

W-22902839

Cluster node IDs are no longer generated with negative values.

W-22294724

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

W-22434375

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

W-22279521

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

W-20824537

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

W-22772644

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

W-22918240

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

W-22969411

Project versions defined with properties are now resolved recursively.

W-22845430

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

W-22817376

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

W-23052713

SDK sources that don’t implement Reconnectable are no longer restarted during graceful shutdown.

W-21563258

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

W-22219018

Sensitive headers are no longer forwarded when an HTTP request is redirected to a different host. This can be configured with FILTER_SENSITIVE_HEADERS_ON_REDIRECT.

W-21045658

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

W-22568982

The Joda-Time library is upgraded to 2.13.0.

W-3300013

The Rhino library is upgraded to 1.7.15.1.

W-22805996

The Apache Neethi library is upgraded to 3.2.1.

W-22805997

The OpenTelemetry API library is upgraded to 1.62.0.

W-22806011

The Apache CXF library is upgraded to 3.5.11.

W-23037585

The c3p0 library is upgraded to 0.14.1.

W-23012711

The Bitronix Transaction Manager library is upgraded to 2.1.21.

W-22405007
DataWeave 2.6.28 is bundled with the Mule 4.6.32 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

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

W-22914494

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

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

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

W-22248198

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

W-22496803

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

W-22248534

Race conditions in outerFluxCompletionScheduler no longer occur during graceful shutdown.

W-22343018

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

W-22373641

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

W-22276522

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

W-22343705

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

W-21193046

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

W-21666905

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

W-21525972

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

W-21882516

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

W-17714668

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

W-22623626

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

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

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

W-22417507
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#may-2026)May 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.30 includes Runtime Manager agent 2.7.13. See [Runtime Manager Agent 2.7.13 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-13). 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:
Issue Resolution ID

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

W-11453332

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

W-18034452

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

W-21337433

The plexus-utils library is upgraded to 4.0.3.

W-21774430

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

W-22013292

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

W-20880559

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

W-21177224

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

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

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

W-21614817
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#april-2026)April 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.29 includes Runtime Manager agent 2.7.11. See [Runtime Manager Agent 2.7.11 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-11). Feature Flagging Mechanism: - Mule 4.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:
Issue Resolution ID

The c3p0 library is upgraded to 0.12.0.

W-21391116

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

W-21391115

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

W-20256082

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

W-20267296

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

W-20791354

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

W-19811593

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

W-21250126

Scheduler jobs no longer deadlock during flow shutdown.

W-21263748

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

W-20038933
DataWeave 2.6.25 is bundled with the Mule 4.6.29 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

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

W-21415439

The Jakarta Mail library is upgraded to 2.1.5.

W-21320250

The range operator now returns null for invalid ranges.

W-21781423
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#march-2026)March 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.6.28 includes Runtime Manager agent 2.7.10. See [Runtime Manager Agent 2.7.10 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-10). Feature Flagging Mechanism: - Mule 4.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:
Issue Resolution ID

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

W-20890587

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

W-20890613

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

W-21001749

Public flows now stop concurrently during graceful shutdown.

W-21228085

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

W-21231834

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

W-21232374

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

W-17689958

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

W-21215761

The tika-core library is upgraded to 3.2.3.

W-21179465

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

W-20633888

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

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

The Array range selector operator no longer experiences performance degradation.

W-20220578

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

W-21045501
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#february-2026)February 2026 ### [](#patch-4-6-27)Patch 4.6.27 - This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990. ### [](#patch-4-6-26)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/jp/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:
Issue Resolution ID

JDK Flight Recorder (JFR) is now disabled by default.

W-19990145

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.

W-20283146

Mule application unresponsiveness no longer occurs after a policy that uses the until-successful component is undeployed or redeployed.

W-20628990

Implemented minor improvements to Mule classloading structures to enhance efficiency and stability.

W-20028988

Thread Context Classloader (TCCL) is no longer wrongly set to the connector after an operation policy execute-next.

W-20618734

Fastutil is now replaced with fastutil-core.

W-20729870
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#january-2026)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/jp/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/jp/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:
Issue Resolution ID

Batch jobs no longer hang when errors occur in steps that use try scopes with global error handlers.

W-17738563

Design-time operations on primary content parameters with non-Java types now work correctly.

W-20187776

Logging information is now improved during graceful shutdown.

W-20278970

A deadlock between Log4j Mule log support during application initialization no longer occurs.

W-20419795

MUnit tests no longer fail intermittently when running on Java 17.

W-17044721

Batch processing no longer fails with serialization error when LDAP action throws an error in Java 17.

W-19524600

Dynamic configurations now work correctly during initialization when using hashCode and equals methods on a TLSConfiguration class.

W-18835469
DataWeave 2.6.22 is bundled with the Mule 4.6.25 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

The stream reader now processes input with multi-byte characters correctly.

W-20016549

The org.apache.commons:commons-text library is upgraded to 1.14.0.

W-20618375

Each variable is now extracted from vars, allowing its materialization to be managed individually. The mule.dw.enable_vars_materialization_pass compatibility flag is added to preserve the previous materialization behavior.

W-19580992 / W-17167283
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#november-2025)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/jp/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:
Issue Resolution ID

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

W-19784910

UndeclaredThrowableException errors no longer occur during Bitronix reconnection.

W-15196888

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

W-18563387

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

W-18912999

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

W-17935223

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

W-18964335

The until-successful scope now properly honors the graceful shutdown timeout. In versions earlier than 4.11.0, you must enable this behavior using these system properties: mule.untilSuccessful.retryOnCriticalError.disallow=true and mule.forcefulShutdown.raiseCancelledError=true.

W-19340663

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

W-18584560

IllegalAccessException no longer thrown when DW serializes error.errorMessage in Scatter-Gather error route.

W-19340663

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

W-16565012

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

W-19802474
DataWeave 2.6.20 is bundled with the Mule 4.6.24 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

The Apache Commons Lang dependency is removed from the distribution.

W-19803454

Materialization errors no longer occur when running functions.

W-19884071
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#october-2025)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/jp/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:
Issue Resolution ID

The org.springframework library is upgraded to 5.3.45.

W-18603096

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

W-17857080

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

W-18667744

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

W-18347293

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

W-19675881

This release reverts the changes introduced in W-17340911.

W-17340911

Cookies now propagate correctly across multiple redirect scenarios.

W-18971065

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

W-17935223

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

W-19407164
DataWeave 2.6.19 is bundled with the Mule 4.6.23 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

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

W-19168279

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

W-19477334

Module compilation performance is improved when running concurrently.

W-19376546
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#september-2025)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/jp/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:
Issue Resolution ID

TLS configuration for FIPS-140-2 is now upgraded.

W-16315176

Applications using Scheduler component in a strict FIPS-140-2 environment no longer fail to deploy due to the unavailability of the MD5 algorithm.

W-19319437

OAuth token is now refreshed when used through ExtensionClient.

W-19248279
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#august-2025)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/jp/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:
Issue Resolution ID

Silent errors and hangs no longer occur when a component fails to start within a foreach/subflow combination.

W-18589595

An incorrect error level message no longer shows during deployment when using APIKit with no flow mappings.

W-19004884

Performance degradation no longer occurs when using repeatable streaming.

W-19175330
DataWeave 2.6.17 is bundled with the Mule 4.6.21 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

A stackOverflowException error no longer occurs during materialization.

W-18981240

The distinctBy function in dw::core::Core now works as expected when used with a CSV input.

W-18990604

DataWeave runtime types are now correctly written when outputting Java.

W-18942349

Access to multipart content raw value no longer reads the part content.

W-18892158

The sizeOf function now works correctly in DataWeave 2.6.14 and later.

W-18850597

The orderBy function now evaluates ordering criteria only when required.

W-18851259

The fromCharCode function now works as expected.

W-17204482
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#july-2025)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/jp/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:
Issue Resolution ID

Schedulers are no longer triggered during graceful shutdown.

W-17981248

The commons-beanutils:commons-beanutils library is upgraded to v1.11.0.

W-18687846

The com.google.code.gson:gson library is upgraded to v2.12.1.

W-17896347

Repeatable streams now make data available before the buffer is full. To enable this behavior, set the system property mule.repeatableStreaming.bytes.eagerRead to true.

W-18716253

Serialization now works correctly with API Gateway internal classes.

W-18475283

The W-17340911 fix, which resolved loader constraint violation errors related to http-connector dependencies in both the domain and the policy, has now been reverted to restore the previous behavior.

W-18327141
DataWeave 2.6.16 is bundled with the Mule 4.6.20 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

This patch update reverts the fix.

W-17167283

XML encoding detection now works correctly when the declaration header is missing.

W-18853667

The fromCharCode function in dw::core::Strings. now manages surrogate characters correctly.

W-17204482

Unicode characters now render correctly at the beginning of the string when using the DataWeave writer function with the onlyData flag enabled.

W-14855645

The Apache POI library is now upgraded.

W-18253747

Experimental warning messages are no longer logged on DataWeave SDK files.

W-16384926
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#june-2025)June 2025 ### [](#patch-4-6-19)Patch 4.6.19 - This patch update reverts the fixes for the following Mule issue: W-17703164 ### [](#patch-4-6-18)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/jp/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:
Issue Resolution ID

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

W-17340911

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

W-17774685

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

W-18388443

Spring Framework artifacts are replaced with vendor-supported equivalents to improve long-term compatibility.

W-18462316

A serialization exception no longer occurs when using caching scope.

W-17703164
DataWeave 2.6.15 is bundled with the Mule 4.6.18 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

The performance of the orderBy function is now improved.

W-18439576

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

W-17147598

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

W-18472194
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#may-2025)May 2025 ### [](#patch-4-6-17)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:
Issue Resolution ID

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

W-18528551
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ### [](#patch-4-6-16)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/jp/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:
Issue Resolution ID

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

W-17980769

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

W-18057570

Parameters field isn’t serialized in InternalEventImplementation.

W-17703164

Connectivity tests in MTS are now fixed for Java 17.

W-18075077

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

W-17846088

The expressionExecutor in adapter is no longer disposed more than once.

W-16263266

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

W-17896357

xerces-j is upgraded to 2.12.2.

W-16980865

raml-parser is upgraded to v1.0.44-17.

W-17750714
DataWeave 2.6.14 is bundled with the Mule 4.6.16 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

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

W-17167283

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

W-18020856

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

W-17670504

DataWeave no longer returns a format error on readUnquotedString.

W-18118138

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

W-17644871

Performance issues no longer occur when using the Mule API Java class Message in DataWeave scripts.

W-18034217

DataWeave now preserves trailing zeroes of single-element sum.

W-17283050
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#april-2025)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/jp/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:
Issue Resolution ID

xerces-J is now updated to v2.12.2.

W-16980865

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

W-17339304

DuplicateMessageException is now correctly serialized with Kryo.

W-17844603

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

W-17340620

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

W-17896358
There is no DataWeave update for this version. For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#march-2025)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/jp/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:
Issue Resolution ID

Resources are now properly released after a timeout when using the Scatter-Gather or Parallel For Each routers. The mule.forkJoin.completeChildContextsOnTimeout feature flag is now added to enable this behavior.

W-16941297

MessagingException can now be converted to JSON using DataWeave.

W-16629236

grizzly-ahc is now upgraded in HTTP Service.

W-17667949

Performance degradation no longer occurs when the nonBlockingWriter is enabled for response streaming.

W-17627284

A race condition introduced by W-17048606 no longer occurs, where the last part of the response body was truncated when streamResponse flag is set to true in request-connection.

W-17617940

Serialization using Object Store V2 with OAuth2 Provider now works as expected.

W-16673760

Performance during cache scope execution is now improved.

W-17671126
DataWeave 2.6.12 is bundled with the Mule 4.6.14 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

The Flat File Module now supports YAML files with nested depth greater than 50.

W-17495145

xerces-j is now updated to 2.12.2.

W-16918194
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#february-2025)February 2025 ### [](#patch-4-6-13)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:
Issue Resolution ID

ConfigurationException no longer occurs while performing Amazon DynamoDB Connector operations.

W-17801971
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ### [](#patch-4-6-12)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/jp/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:
Issue Resolution ID

InterceptionException is no longer thrown while running MUnit test containing a batch job.

W-17395302

The optimization to avoid sending body contents on NTLM type 1 requests added in W-17107281 is now controlled by the feature flag mule.ntlm.avoid.send.payload.on.type1.

W-17216089

A ClassCastException thrown when an error occurs within an on-error-continue component no longer prevents transactions from rolling back.

W-17430963

A corner case has been fixed and Anypoint Monitoring dashboard now correctly shows all metrics.

W-16828516

Kryo serialization issue no longer occurs in Java 17 when running with distributed cluster using authentication, caching policy, and persistent Object Store.

W-16912085

Transactions initiated before a flow-ref call are now rolled back in the correct place if an error propagates from the flow-ref.

W-17453707

API metrics are now properly sent.

W-17529530
DataWeave 2.6.11 is bundled with the Mule 4.6.12 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

The Java reflection lookup strategy is now improved for bean instances.

W-17624594

Compatibility flags created with Mule runtime 4.4 can now be used with older Mule runtime versions.

W-17372664

The deconstruct pattern now works as expected when using append on empty objects combined.

W-16823030
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#january-2025)January 2025 ### [](#patch-4-6-11)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)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/jp/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:
Issue Resolution ID

Windows no longer throws cannot delete file errors during application undeploy.

W-17050930

BufferOverFlowException with inter-node communication getting stuck no longer occurs when using clusters with encryption under heavy load.

W-16517561

Unnecessary internal blocking operations no longer occur when handling large streamed HTTP responses.

W-17048606

Body content is no longer sent on Type 1 requests during NTLM authentication.

W-17107281

Deploying applications that contain XML SDK connectors no longer causes application class loader memory leak.

W-16814280

An infinite loop no longer ocurrs when a redelivery policy is exhausted in a source configured with Transactions and contains an On Error Propagate.

W-17403761

ConnectionException no longer occurs when using batch processing.

W-17008722

A memory leak no longer occurs when using mule-validation-module.

W-16789548

MessageProcessorNotificationListener is no longer called multiple times when running MUnit suites.

W-11866494

A serialization error no longer occurs in Java 17 when using clustering mode or Object Store v2.

W-17218707

IllegalAccessException is no longer thrown during cache scope serialization with Kryo.

W-17089503

All transactions running within a global Error Handler are now committed as expected.

W-16619771
DataWeave 2.6.10 is bundled with the Mule 4.6.10 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

Compatibility flags created with Mule runtime 4.4 can now be used with older Mule runtime versions.

W-17372664

The deconstruct pattern now works as expected when using append on empty objects combined.

W-16823030

The Java reflection lookup strategy is now improved for bean instances.

W-17206423
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#november-2024)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/jp/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:
Issue Resolution ID

Memory leak in MuleApplicationClassloader no longer occurs while undeploying an application.

W-16823349

A batch serialization error no longer occurs in Java 17 when one of the steps throws SQLException.

W-16546951

A deadlock no longer occurs when consuming the payload in the completion callback of the HTTP client sendAsync method.

W-16640190

NullPointerException no longer occurs when undeploying an application with native libraries in Windows OS.

W-16712841

Log4j2 monorepo is upgraded to 2.24.1.

W-16889265

The commons-io:commons-io dependency is upgraded to 2.17.0.

W-16843119
DataWeave 2.6.9 is bundled with the Mule 4.6.9 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

The stripTrailingZeroes compatibility flag is now added to preserve the decimal format.

W-17030593

Apache POI folder used for temporal files is no longer deleted.

W-16899674
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#october-2024)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/jp/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:
Issue Resolution ID

Spring Core is upgraded to 5.3.39.

W-16519084

The configuration-properties encoding parameter is no longer ignored.

W-12228892

Web Service Consumer Connector and RosettaNet Connector no longer fails when there is an HTTP TLS transport configuration.

W-16288302

InitialisationException is no longer thrown when using the Raise Error component with an extra space at the end of the type field.

W-16237424

Kryo serialization now works as expected with ResourceOwnerOAuthContextWithRefreshState when using Java 17.

W-16533466

Kryo serialization now works as expected when executing the Rate Limit policy in Java17.

W-16843706

Fatal errors no longer occur when loading native libraries in Java 17.

W-16787783

java.lang.InstantiationError : java.util.Map is no longer thrown when applying an authentication policy.

W-16595277

When the feature flag anypoint.platform.keep.default.policy.format is set to true or the policy minimum Mule version is 4.5.0, the policy name format is now ${policyName} @ ${artifactName} - ${flowName}.

W-16169887

Logging for the Analytics .db files cleanup is now improved.

W-16624763

grizzly-ahc is now upgraded in the HTTP service.

W-16734361

Race condition now causes an infinite loop in Grizzly AHC.

W-16599945
DataWeave 2.6.8 is bundled with the Mule 4.6.8 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

DataWeave descendant selector performance is now improved.

W-16343577

Streaming capability for arguments at sum, countBy, and sumBy functions is now enabled.

W-16125755

Input/output MimeType properties are now preserved as expected.

W-16161736

Access error for Java 17 encapsulation errors is now improved.

W-15705596

Coercion error is now caught inside try as expected.

W-15323897
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#september-2024)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:
Issue Resolution ID

NullPointerException is no longer thrown when DataWeave transforms a RetryPolicyExhaustedException to a JSON format on a Java 17 runtime.

W-15643200

Properties files are now located in the lib/user directory during application deployment.

W-16404468

com.google.gson.stream.MalformedJsonException is no longer thrown while deploying an application.

W-16343071

Debug logs for custom policies containing a custom extension/connector now work correctly.

W-15286605

The process of unloading native libraries in Windows OS running on Java 8 and Java 11 is now improved.

W-16375439

cxfVersion is upgraded to 3.5.9.

W-16436783

JaCoCo is upgraded to 0.8.11.

W-14866639

maven-jar-plugin is upgraded to 3.3.0.

W-14580541

Policies with minimum Mule version 4.4.0 now use the flow name as part of the artifact name, when the feature flag anypoint.platform.keep.default.policy.format=true is set.

W-16169887

NullPointerException is no longer thrown when API Gateway tries to dispose an empty cluster.

W-16540685

API Gateway pollers are no longer initialized when the API Gateway is started in offline mode.

W-16093885

Race condition no longer causes byte buffer disposal errors when deploying policies.

W-16450677
DataWeave 2.6.7 is bundled with the Mule 4.6.7 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

DataWeave now preserves MimeType properties correctly.

W-16161736
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#august-2024)August 2024 Patch release version: 4.6.6 This patch update addresses the following Mule issues:
Issue Resolution ID

Loaded native libraries are now copied into a separate temporary folder to avoid issues while redeploying applications in Windows OS.

W-15894519

Parameter resolution error handling is no longer affected when the parameterized operation is inside a dynamically referenced subflow.

W-15923581

The OAuth token invalidation status is now communicated to other nodes in a cluster when a token is invalidated on one node.

W-15154658

Flows now honour the state configured in flows.deployment.properties when restarting the app, regardless of the initial state. To enable this feature, use the mule.honour.persisted.flow.state system property. This only applies to Standalone and Hybrid deployments.

W-15750334

Mule runtime startup no longer fails when MULE_HOME has a blank space on Windows OS.

W-15346051

A serialization exception is no longer thrown when a Batch Step fails with a ModuleException in Java 17.

W-15808825

mule-script-module is now improved to ensure that beans no longer contain invalid references to injected dependencies, whether they are directly or indirectly reliant on MuleConfiguration.

W-15832941

Jars in lib/user are now visible from jars in lib/opt. For example, using cluster persistence with the JDBC driver provided in lib/user no longer fails with a Could not load driverClass error.

W-16010357

Serialization now works as expected with Batch Job and Salesforce BulkOperationResult in Java 17.

W-16105403

Batch module no longer fails with a Could not serialize object error when client ID enforcement policy is enabled.

W-16124318

Deploying a policy no longer fails while using a mule directory with whitespaces.

W-15440100

ClassNotFoundException is no longer thrown when upgrading from Mule runtime 4.4.0 using the OAuth 2 authentication code and Object Store V2 stored tokens.

W-15595791

NullPointerException no longer occurs when having MQ connector as a dependency in MUnit 3.1.0.

W-15734679

API Gateway initialization no longer fails if quorum isn’t reached in cluster mode.

W-15951155

Hard timeout for platform requests is now available by setting up the anypoint.platform.request_timeout in milliseconds.

W-16141554
DataWeave 2.6.6 is bundled with the Mule 4.6.6 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

Argument materialization is now improved at the dw::Runtime::try function.

W-15323897

Streaming capability is now enabled for arguments of sum, countBy, and sumBy functions.

W-16125755
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#july-2024)July 2024 Patch release version: 4.6.5 This patch update addresses the following Mule issues:
Issue Resolution ID

The mule-assembly-content-descriptor file size no longer differs between mule-ee-distribution-standalone ZIP and Tar GZ distributions.

W-15397610

The redeployment of an app with a domain using a Groovy component no longer throws the groovy.lang.MissingMethodException exception.

W-15750766

Batch job instance queue store files are removed after completion.

W-15546969

Cache scope with multiple computations no longer occurs if events arrive concurrently for an absent key.

W-14604517

Tanuki wrapper configuration is now enabled for AArch64.

W-15839796

MDC context is reset after the XML SDK operation is executed.

W-15206528

MUnit tests no longer fail with groupId cannot be null when using a parent POM for dependencies and plugins.

W-14998254

Maven plugin versions are updated to be compatible with Maven 3.9.

W-15554914

JRuby dependency is upgraded to 9.4.7.0.

W-15757000

Deploying a policy in Windows no longer fails in folders containing whitespaces.

W-16112611

Open Telemetry tracing support is now added to policies.

W-15633203

Kerberos is now enabled for proxy authentication against Anypoint Platform for Gateway capabilities.

W-15642605

Default stronger validations for policies are now added after applying the property anypoint.platform.validate_policy_schemas.

W-15769926

Logging for Gateway Analytics initialization is now improved.

W-15904845

Handling of connection errors with API platform is now improved.

W-15809377

Default gatekeeping for APIs that fail when doing a rollback is now added using the property anypoint.platform.gatekeeper.block_failed_revert.

W-15427352
DataWeave 2.6.5 is bundled with the Mule 4.6.5 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

Enforced Java accessibility restrictions only for Mule apps with DataWeave language level version 2.6 and later and executing with Java 17 and later.

W-15832793

Materialization issues no longer occur with schema properties.

W-15839190

The Flat File module now adds the substituteCharacterAsMissingValue reader property.

W-15571377

The Flat File module now adds the fillRedefinesByMaxLength writer property.

W-15973636
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#june-2024)June 2024 Patch release version: 4.6.4 This patch update addresses the following Mule issues:
Issue Resolution ID

Applications configured with OAuth and running on Java 17 are now correctly serialized.

W-15425364

You can now see the number of flows considered for UBP and what those flows are when the application starts.

W-14401338

plexus-archiver is upgraded to 4.9.1.

W-14821825

The version in the pom.xml file is now parsed when containing the property ${text}.

W-15228973

Events with statistics are now correctly serialized for applications running on Java 17.

W-15542604

The exception java.lang.IllegalAccessException no longer occurs when using itemSequenceInfo in DataWeave.

W-15617764

DataWeave compiled expressions cache is no longer overpopulated when using nested templates.

W-15782010

Batch job serialization now works as expected when running on Java 17.

W-15345812

Tracing variables inside XML operations are no longer propagated to the flows.

W-15206528

jackson-databind is upgraded to 2.15.4.

W-15628361

NullPointerException no longer occurs on AST-deserialized applications using Anypoint Custom Metrics Connector.

W-15677894

Resiliency is now improved on policy application and updates.

W-15426519
DataWeave 2.6.4 is bundled with the Mule 4.6.4 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

A java.io.IOException exception no longer occurs when writing the same binary input multiple times for JSON and XML formats.

W-14589732

The Excel writer now generates XLSX files using ZIP specification 2.0.

W-15534640

When comparing a Date with a String representation of a date, the Date format is now used to coerce the String accordingly.

W-15478713

Access error messages for Java 17 encapsulation errors are now improved.

W-15705596
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#may-2024)May 2024 Patch release version: 4.6.3 This patch update addresses the following Mule issues:
Issue Resolution ID

Client, policy, and API names are now shown when logging Analytics events.

W-15294568

When upgrading a policy, templates are now downloaded before the previous version is removed.

W-15212679

When applying a policy that initially failed but was later applied successfully, the retry initiated by the gateway no longer causes an exception error.

W-15186491

Joda-Time is upgraded to v2.12.7.

W-15511864

Apache CXF is upgraded to version 3.5.8.

W-15293232

Getting metadata from a XSD with vc:minVersion=1.1 no longer causes a NullPointerException error.

W-15193303
DataWeave 2.6.3 is bundled with the Mule 4.6.3 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

ArithmeticException no longer executes toHex with non-integer numbers.

W-15006840

Performance degradation no longer occurs when an array is concatenated.

W-15399854
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#april-2024)April 2024 Patch release version: 4.6.2 This patch update addresses the following Mule issues:
Issue Resolution ID

NullPointerException no longer occurs when deploying domains.

W-15159880

Hazelcast is upgraded to 5.2.5.

W-15274674

Spring is upgraded to 5.3.33.

W-15260752

GraalJS is upgraded to 22.3.5.

W-15284493

MUnit tests using tracing module and "Set logging variable" now work as expected.

W-14773408

Using vc:minVersion="1.1" in XSD schema no longer throws NullPointerException in XML SDK connectors.

W-15081363

Template parser validation is now improved.

W-15141905
DataWeave 2.6.2 is bundled with the Mule 4.6.2 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

Inconsistent behavior no longer occurs between in-memory and streaming XML parsers for deciding document encoding.

W-15110015

Streaming for DataWeave-based data formats like ndjson now works as expected.

W-15262860

The Excel reader no longer reads furigana characters.

W-14991276

Coercion of the third parameter on the ternary function executor now works as expected.

W-15061008
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#march-2024)March 2024 Patch release version: 4.6.1 This patch update addresses the following Mule issues:
Issue Resolution ID

Performance is now improved for certain For Each scenarios.

W-14678431

HTTP Request Connector no longer throws Connection limit exceeded, cannot process request when maxConnections is set to 1.

W-14686211

Disabling the enableNotifications flag on the On Error Continue component now works as expected.

W-14954677

Multi-step batch jobs can now be correctly resumed and finished after being stopped.

W-14726677

The error message is now improved for exceptions that occur when loading an extension because of Java version incompatibility.

W-14934626

The error message namespace already exists is no longer thrown when using the same namespace with the current module or extension namespace for apps using the XML SDK component.

W-14559071

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 mule.tx.error.when.timeout feature flag.

W-14128870

Memory leaks no longer occur when using the mule-scripting-module dependency with HTTP Connector.

W-14479158

Java JDK inlineDeclaration now resolves correctly for stateless subtypes.

W-14645134
DataWeave 2.6.1 is bundled with the Mule 4.6.1 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

Performance is now improved when coercing addition and subtraction operations.

W-14927555
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#february-6-2024)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/jp/release-notes/mule-runtime/java-adoption).
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/jp/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/jp/general/java-support#policies) and [Upgrading API Proxies](https://docs.mulesoft.com/jp/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/jp/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/jp/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/jp/general/java-support#custom-connectors). - Java SDK now includes the new `@JavaVersionSupport` annotation. See [Supported Java Version Concept](https://docs.mulesoft.com/jp/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)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:
Issue Resolution ID

aspectj is now removed from distribution.

W-13913357

The Joda-Time library is upgraded to version 2.12.5.

W-13913362

The GraalJS library is upgraded to 22.3.3.

W-13961780

MUnit no longer fails with apps using Anypoint Connector for DotNet (DotNet Connector).

W-14747448

NullPointerException no longer occurs in XSD parsing when a schema has a minVersion/maxVersion.

W-14748090

Timeout is not considered for local transactions and rollbacks are silently executed.

W-14608096

MediaType cache now has a maximum size to prevent leaks.

W-14490182

DataWeave now uses objects as part of the Mule API.

W-14185880

License installation no longer fails with FileNotFoundException.

W-14542349

Legacy properties builder no longer reevaluates from root resolver placeholders.

W-14616618

JAVA_HOME is now properly handled by Surefire.

W-12082402

HTTP Redirect no longer works on Mule runtime 4.x on HTTP Post.

W-14619216

Race condition no longer results in NullPointerException when the Write Queue is full.

W-14543363

Container of the Embedded Runtime no longer stops if it wasn’t created.

W-14321634

Unnecessary MBeans for JMX management are no longer registered.

W-12422473

Internal dependency graph is now generated only once for all validations.

W-12421187

Extension model parsing no longer fails for extensions with dependencies declared as provided.

W-14646484
DataWeave 2.6.0 is bundled with the Mule 4.6.0 release. This release addresses the following DataWeave issues:
Issue Resolution ID

Caching now works correctly when coercing for addition and subtraction operations.

W-14591653

do scope declarations with pattern matching now properly reflect variable names when variables are optimized with common subexpression elimination.

W-14514837

The minInflateRatio property is now added to Excel format to control the zip bomb check threshold.

W-14315728
### [](#bundled-components)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/jp/release-notes/mule-runtime/mule-esb#mule-upgrades). To ensure optimal performance with this version of Mule and avoid unexpected issues, update these modules and extensions to their latest version at the time of this release:
Module or Extension Version

APIkit for Mule 4

1.10.1

APIkit for OData

2.2.1

APIkit for OData 4

1.3.4

APIkit for SOAP

1.4.1

APIkit for GraphQL

1.0.0

Spring module

1.3.11

MUnit plugin

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