--- schema_version: "1" id: a94d76d251cfeb7dd02410032c549dd8f518a4da181232857917e57fe590c3e0 title: Mule Runtime Engine 4.9.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.9.0-release-notes.md canonical_url: https://docs.mulesoft.com/jp/release-notes/mule-runtime/mule-4.9.0-release-notes source_site: docs.mulesoft.com content_type: documentation content_hash: c63fd78128c9564112bbbf6757a5e86072fe679eb5144901c440ea23106273e2 description: MuleSoft Documentation Site latest: true --- # Mule Runtime Engine 4.9.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-9-23)Patch 4.9.23 The October patch update 4.9.23 addresses regressions in the October patch update 4.9.22.
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-9-22)Patch 4.9.22 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.22 includes Runtime Manager agent 2.8.5. See [Runtime Manager Agent 2.8.5 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-5). ### Fixed Issues Patch release version: 4.9.22 This patch update addresses these Mule issues:
Issue Resolution ID

The Reactor Core library is upgraded to 3.8.7.

W-23953702

The Jackson library is upgraded to 2.22.3.

W-24335732

The Netty library is upgraded to 4.2.18.Final.

W-24336011

The Apache Neethi library is upgraded to 3.2.4.

W-24335736

The Spring Framework library is upgraded to 7.0.9.

W-24232049

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

Reads from the repeatable streaming buffer are now lock-free when data is already available, reducing thread contention. You can control this behavior by using the mule.repeatableStreaming.lockFreeRead system property.

W-24012839

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

You can now configure a full request timeout for the HTTP server by using the mule.http.server.fullRequestTimeout system property, in milliseconds. This property is disabled by default.

W-22040113

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

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

W-23716301

HTTP/1-only HTTPS listeners backed by the Netty HTTP service no longer fail to establish TLS connections when an application loads the Bouncy Castle JSSE provider from a shared library outside the runtime’s classloader.

W-23355657

The Netty-based HTTP client now defers DNS resolution of the target host to the proxy when a proxy is configured, regardless of the configured scheme.

W-24010245

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. You can change this behavior by configuring 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.9.21 includes Runtime Manager agent 2.8.4. See [Runtime Manager Agent 2.8.4 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-4). 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.9.21 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 disposed source policy is no longer left in the policy cache when a flow is stopped and restarted while cache population and flow-stop invalidation occur concurrently.

W-23564125

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

A malformed authorization URL no longer occurs when the configured OAuth authorizationUrl contains an existing query parameter.

W-23064254

The HTTP client configurer now includes a method to control whether sensitive headers are filtered when a request is redirected to a different domain.

W-21045658

A forward-proxy client no longer sends a malformed, path-only request line.

W-23384645

A worker thread no longer hangs indefinitely, eventually exhausting the runtime’s thread pool, when a client drops the connection while its HTTP request body is being read.

W-23612974

Netty-based HTTP client requests no longer fail when the response contains a header section larger than 8 KB and a larger response header size limit is configured.

W-23443375

DIGEST authentication in the Netty-based HTTP client no longer fails with a 401 Unauthorized response when the server issues an RFC 7616-compliant challenge.

W-23075291

A NullPointerException no longer occurs during cluster node discovery when using PCF or Kubernetes-based cluster discovery.

W-23466789

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 Netty library is upgraded to 4.2.17.Final.

W-3300013

The Jackson library is upgraded to 2.22.1.

W-23540341

The RAML Parser library is upgraded to 2-1.2.1.

W-23328348

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

Worker TLS configuration for Government Cloud is strengthened.

W-23819316
DataWeave 2.9.18 is bundled with the Mule 4.9.21 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

Vulnerable dependencies are upgraded to address reported security vulnerabilities.

W-23924223

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.9.20 includes Runtime Manager agent 2.8.3. See [Runtime Manager Agent 2.8.3 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.8.x-release-notes#2-8-3). 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.9.20 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

HTTP/3 requests sent to an HTTP/1 server now correctly fail with a 505 (HTTP Version Not Supported) response.

W-23029577

Requests with a non-numeric Content-Length header are now rejected with a 400 (Bad Request) response.

W-23029480

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

When running in FIPS mode on a standalone server, the runtime now logs a warning at startup if the JVM java.security file isn’t configured with the required FIPS providers, instead of silently masking the misconfiguration.

W-22794711

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-23131090
DataWeave 2.9.17 is bundled with the Mule 4.9.20 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

The per_app_java_bean_cache compatibility flag now correctly reports its creation version as 2.9.

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). ## [](#july-2026)July 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.19 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.9 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.9.19 This patch update addresses these Mule issues:
Issue Resolution ID

Cluster node IDs are no longer generated with negative values.

W-22294724

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

W-22434375

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

W-22279521

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

W-20824537

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

W-22772644

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

W-22918240

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

W-22969411

Project versions defined with properties are now resolved recursively.

W-22845430

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

W-22817376

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

W-22470584

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

W-23052713

The Content-Length header is now removed based on the actual entity byte length.

W-22570070

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

The Jackson Databind library is upgraded to 2.21.4.

W-3300013

The OpenTelemetry API library is upgraded to 1.62.0.

W-22806027

The c3p0 library is upgraded to 0.14.1.

W-23012713

The Apache Neethi library is upgraded to 3.2.1.

W-22939389

The Apache CXF library is upgraded to 3.6.11.

W-23037617

The Rhino library is upgraded to 1.8.1.

W-22939391

The Log4j library is upgraded to 2.25.4.

W-22939403

The Reactor Netty library is upgraded to 1.2.18.

W-22939384

The Spring Framework is upgraded to 6.2.19.

W-22956997

The Netty library is upgraded to 4.2.15.Final.

W-22956998

The Bitronix Transaction Manager library is upgraded to 2.1.21.

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

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

W-22914494

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

W-22364385
For guidance with the patching process, see [Apply Patch Updates](https://docs.mulesoft.com/jp/release-notes/mule-runtime/patching-mule-versions#apply_patch_updates). ## [](#june-2026)June 2026 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.18 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.9.18 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

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.9.15 is bundled with the Mule 4.9.18 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

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

W-21712344

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

W-22417507
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.9.17 includes Runtime Manager agent 2.7.13. See [Runtime Manager Agent 2.7.13 Release Notes](https://docs.mulesoft.com/jp/release-notes/runtime-manager-agent/runtime-manager-agent-2.7.x-release-notes#2-7-13). FIPS 140-3 Compliance Support: - You can now configure Mule runtime to operate in a FIPS 140-3-compliant environment using certified cryptography providers. See [FIPS 140-3 Compliance Support](https://docs.mulesoft.com/mule-runtime/latest/fips-140-3-compliance-support) for more information. General improvements: - The `diaf` Event Dump now includes two additional `eventContextState` values: `PENDING` and `WAITING_NON_BLOCKING`. See [Mule Troubleshooting Plugin](https://docs.mulesoft.com/mule-runtime/latest/mule-troubleshooting-plugin) for more information. ### Fixed Issues Patch release version: 4.9.17 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

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

W-21632770

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

W-21860840

The Netty library is upgraded to 4.2.12.Final.

W-21795152

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

W-17714668

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

W-22013292

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

W-20880559

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.9.14 is bundled with the Mule 4.9.17 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.9.16 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.9 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.9.16 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

The Jackson Core library is upgraded to 2.18.6.

W-21420104

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

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

W-21184863

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

W-21321115

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

W-21465366

Netty response timeout behavior is now consistent with Grizzly.

W-21547186

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

W-21428392

Netty HTTP Client now filters duplicate Content-Type headers.

W-21344116

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

W-21515340
DataWeave 2.9.13 is bundled with the Mule 4.9.16 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.9.15 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.9 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.9.15 This patch update addresses these Mule issues:
Issue Resolution ID

The jakarta.mail library is upgraded to 1.6.8.

W-21138257

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

W-20890587

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

W-20890613

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

W-21001749

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

W-21220031

Public flows now stop concurrently during graceful shutdown.

W-21228085

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

W-21231834

Errors that are not MessagingException errors are no longer silenced.

W-21043969

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." errors no longer occur 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 "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.9.12 is bundled with the Mule 4.9.15 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-9-14)Patch 4.9.14 - This patch update reverts the fixes for these Mule issues: W-20618734 and W-20628990. ### [](#patch-4-9-13)Patch 4.9.13 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.13 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.9.13 This patch update addresses these Mule issues:
Issue Resolution ID

Optimized the logging service to avoid creating unnecessary logging contexts when running a single application.

W-19965379

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

W-19990145

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

W-20028988

Reduced memory consumption by removing deployment-specific objects after application deployment.

W-20053979

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

Optimized the HTTP Service to avoid regenerating static attributes for every request when using Netty.

W-20615232

The io.netty:netty-bom library is upgraded to 4.2.9.Final.

W-3300013

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

W-20679050

Fastutil is now replaced with fastutil-core.

W-20729870
DataWeave 2.9.11 is bundled with the Mule 4.9.13 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

Starting in Mule runtime 4.6, you can now configure materialization settings (mule.dw.enable_vars_materialization_pass).

W-19580992
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.9.12 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.9.12 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

Applications no longer become unresponsive after thread pool exhaustion when using Netty as the HTTP Service implementation with the Anypoint MQ Connector.

W-19806707

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

The HTTP Client can now establish an SSE source when the content-type header doesn’t exactly match text/event-stream.

W-20420476

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.9.10 is bundled with the Mule 4.9.12 release. This patch release addresses these DataWeave issues:
Issue Resolution ID

Functions now materialize correctly when the function body contains a single var declaration.

W-20365331

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

W-20016549
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.9.11 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.9.11 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

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

W-1982570

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

W-19648397

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

W-18584560

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

W-19340663

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

W-16565012

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

W-19802474

SSE clients can now parse events that do not include an event field. These events now default to message, as described in the specification.

W-19667148

The reactor.netty library is upgraded to 1.2.10.

W-17264514

The netty library is upgraded to 4.2.7.Final.

W-19995637

The spring-core library is upgraded to 6.2.11.

W-19674953
DataWeave 2.9.9 is bundled with the Mule 4.9.11 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

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

W-19581017

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). ## [](#october-2025)October 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.10 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.9.10 introduces the Mule Troubleshooting plugin, which generates a structured diagnostic archive (DIAF) to simplify troubleshooting, consolidate runtime metrics, and provide consistent data for MuleSoft Support. It works across all deployment models and helps investigate performance issues, application errors, and scheduler activity. See [Mule Troubleshooting Plugin](https://docs.mulesoft.com/mule-runtime/latest/mule-troubleshooting-plugin) for more information. ### Fixed Issues Patch release version: 4.9.10 This patch update addresses these Mule issues:
Issue Resolution ID

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

W-17857080

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

W-18667744

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

W-18347293

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

W-19675881

Cookies now propagate correctly across multiple redirect scenarios.

W-18971065

The Netty library is upgraded to 4.1.124.Final.

W-19341592

The Handlebars library is upgraded to 4.4.0.

W-19064659

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

W-19383955

The io.netty : netty-codec library is upgraded to 4.1.127.Final.

W-19568278

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

W-19353311

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

W-17264514

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

W-18902280

Scheduler name generation no longer breaks the platform logging aggregator when processor chains have null or empty names.

W-19432758

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

W-19667148

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

W-19471841

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

W-19407164
DataWeave 2.9.8 is bundled with the Mule 4.9.10 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
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.9.9 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.9.9 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

io.projectreactor.netty : reactor-netty-http is upgraded to 1.2.8.

W-19074903

Component annotations, such as location, are no longer overwritten by other components.

W-18269859

org.apache.commons : commons-lang3 is upgraded to 3.18.0.

W-19059553
DataWeave 2.9.7 is bundled with the Mule 4.9.9 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

A memory leak during Weave type schema resolution is now fixed.

W-19389019

Potential deadlocks no longer occur when increasing concurrency while parsing DataWeave scripts.

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). ## [](#august-2025)August 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.8 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.9.8, 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.9.8 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

Logging behavior when combining properties and expressions is reverted to the previous behavior.

W-18822321

Performance degradation no longer occurs when using repeatable streaming.

W-19175330

OAuth token is now refreshed when used through ExtensionClient.

W-19248279
DataWeave 2.9.6 is bundled with the Mule 4.9.8 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
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.9.7 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.9.7 This patch update addresses the following Mule issues:
Issue Resolution ID

DataWeave now correctly serializes CompositeRoutingException to JSON.

W-16562974

The Parser Template now correctly resolves placeholder expressions.

W-16761707

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

W-18687846

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

Schedulers are no longer triggered during graceful shutdown.

W-17981248

OAuth logging is now added when doing token update.

W-18622349

Serialization now works correctly with API Gateway internal classes.

W-18475283
DataWeave 2.9.5 is bundled with the Mule 4.9.7 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 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.6 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). General improvements: - Log4J is upgraded to 2.24.3. ### Fixed Issues Patch release version: 4.9.6 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

A serialization exception no longer occurs when using caching scope.

W-17703164

A classloader leak no longer occurs on undeployment when using lazy service initialization.

W-17750750

The mule.parse.template.use.legacy.default.targetValue compatibility switch is reintroduced to use the legacy default value for the targetValue parameter of the parse-template component. A one-time warning is now logged when enabled.

W-18324755

Preemtive analytics queue deletion is now added.

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

XML encoding is now detected before selecting a parser.

W-17637749

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

CompilationResult no longer retains a reference to the execution frame, which previously caused a memory leak.

W-18288980
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-9-5)Patch 4.9.5 The May patch update 4.9.5 addresses a regression in the previous May patch update, 4.9.4, and includes the fixes in the patch. Patch release version: 4.9.5 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-9-4)Patch 4.9.4 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.4 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.9.4 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/custom WebSocket close codes.

W-17846088

Configuration for preserveHeaderCase is now added in SseSource.

W-18085890

DefaultMessageBuilder no longer contains missing fields.

W-17607446

Contention between transaction and APIkit is now avoided due to tracing initialization.

W-18194349

A schedule is now added to consume the slowly populated pipe to an IO Executor.

W-17444122

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

W-17896357

com.google.code.gson:gson is upgraded to 2.12.1.

W-17896347

com.google.protobuf:protobuf-java is upgraded to v3.25.6.

W-17986761

Custom notifications are now properly dispatched.

W-16091925
DataWeave 2.9.3 is bundled with the Mule 4.9.4 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

DataWeave now preserves trailing zeroes of single-element sum.

W-17283050

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 Message in DataWeave scripts.

W-18034217
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.9.3 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). MuleSoft Government Cloud support coverage: - Government Cloud now supports Mule runtime 4.9. See [Features Included in Government Cloud](https://docs.mulesoft.com/jp/gov-cloud/#features-included-in-government-cloud). ### Fixed Issues Patch release version: 4.9.3 This patch update addresses the following Mule issues:
Issue Resolution ID

The Netty codec library is now updated to 4.1.119.Final.

W-17980407

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

W-17340620

DuplicateMessageException is now correctly serialized with Kryo.

W-17844603

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

W-17339304

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

W-17896358

The mule-sdk-api dependency now contains all the required license information.

W-18033237
DataWeave 2.9.2 is bundled with the Mule 4.9.3 release. This patch release addresses the following DataWeave issues:
Issue Resolution ID

Concurrency issues no longer occur when loading modules.

W-17918619

The flat file module no longer fails when loading files with a 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). ## [](#march-2025)March 2025 ### What’s New Runtime Manager agent: - This release of Mule runtime 4.9.2 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.9 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.9.2 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

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

grizzly-ahc is now upgraded in HTTP Service.

W-17667949

When using sdk-api version of @Connection and ConnectionProvider in a source, a validation saying that @Connection can only be used with the extensions-api version of ConnectionProvider is no longer triggered.

W-17559243

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

W-16912085

Performance during cache scope execution is now improved.

W-17671126

The com.hazelcast:hazelcast dependency is downgraded to 5.2.5.

W-17905862
DataWeave 2.9.1 is bundled with the Mule 4.9.2 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

Consuming values now work as expected when using overloaded materialized functions.

W-17588914
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-9-1)Patch 4.9.1 The February patch update 4.9.1 addresses a regression in the previous February patch update, 4.9.0, and includes the fixes in the patch. Patch release version: 4.9.1 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). ### [](#february-6-2025)February 6, 2025 ### What’s New The 4.9.0 version of Mule runtime introduces the following enhancements: Java adoption: - In Mule 4.9.0 and later, you can compile any Mule project and additional dependencies for Java 17. - You can now run applications on Java 17 only. - This release supports auto minor upgrades for Java 17 apps between Mule 4.8 Edge and Mule 4.9 Edge, as well as from Mule 4.6 LTS to Mule 4.9 LTS. - Java 8 and 11 apps won’t be auto minor upgraded to Mule 4.9, so plan your upgrade path for apps that are running on Java 8 or 11 accordingly. Feature Flagging Mechanism: - Mule 4.9 incorporates new feature flags. See [Feature Flagging Mechanism](https://docs.mulesoft.com/mule-runtime/latest/feature-flagging) for a detailed description of each feature flag and configuration instructions. Runtime Manager agent: - This release of Mule runtime 4.9.0 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). General improvements: - Mule 4.9 upgrades the subset of libraries from included third-party software. See [Third-Party Software in Mule](https://docs.mulesoft.com/mule-runtime/latest/third-party-software-in-mule) for a detailed description. ### [](#dataweave-features)DataWeave Features The 2.9.0 version of DataWeave introduces these new features and enhancements: Extended format support: - DataWeave introduces support for the Event Stream format. See [Event Stream Format](https://docs.mulesoft.com/dataweave/latest/dataweave-formats-eventstream). General improvements: - DataWeave incorporates new system properties. See [DataWeave System Properties](https://docs.mulesoft.com/dataweave/latest/dataweave-system-properties). ### Fixed Issues The release addresses the following Mule issues and incorporates all patch updates from the 4.8.0 Mule release through January 2025:
Issue Resolution ID

Spring is upgraded to 6.2.0.

W-16639197

The org.jgrapht:jgrapht-core is upgraded to v1.5.2.

W-16494546

The com.github.ben-manes.caffeine:caffeine is upgraded to v3.

W-16494569

The plexus-component-annotations is upgraded to v2.2.0.

W-16541666

The org.apache.commons:commons-compress is upgraded to v1.27.0.

W-16515101

The com.hazelcast:hazelcast is upgraded to v5.4.0.

W-16594688

The Xerces-J is upgraded to v2.12.2.

W-16980865

The org.jetbrains:annotations is upgraded to v26.

W-16944403

The kotlin is upgraded to v2.

W-16908778

The org.togglz:togglz-core is upgraded to v4.

W-16881509

The graal-sdk is upgraded to v24.1.1.

W-16772392

The byteBuddy is upgraded to v1.15.1.

W-16778624

The org.apache.xmlbeans:xmlbeans is upgraded to v5.

W-15263392

The com.lmax:disruptor is upgraded to v4.

W-16514909

Compile target is now set to Java 17.

W-16045353

An error message now indicates if a classloader fails to be created for a service.

W-17244755
DataWeave 2.9.0 is bundled with the Mule 4.9.0 release. This release addresses the following DataWeave issues:
Issue Resolution ID

Java module now honors Java bean accessor methods.

W-17142345
### [](#bundled-components)Bundled Components - DataWeave version 2.9.0 - Runtime Manager Agent plugin version 2.6.7 ### 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.11.3

APIkit for OData

2.3.0

APIkit for OData 4

1.5.2

APIkit for SOAP

1.6.0

APIkit for GraphQL

1.1.0

Spring module

1.4

MUnit plugin

3.4.0
### [](#considerations-for-mule-extension-developers)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.9@mule-runtime::mule-troubleshooting-plugin.adoc](#4.9@mule-runtime::mule-troubleshooting-plugin.adoc) - [Known Issues](https://help.salesforce.com/s/issues)