---
schema_version: "1"
id: 47cd2426023e9ae44782f872fe00baf29d65079038635e4c68f606ce7c01a2d0
title: Mule Runtime 4.3.0 Release Notes
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/release-notes/mule-runtime/mule-4.3.0-release-notes.md
canonical_url: https://docs.mulesoft.com/release-notes/mule-runtime/mule-4.3.0-release-notes
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 8a4554469ea2b17658c2f546808cd593f38953b4323f0ac1751c9104f5ce68d3
description: MuleSoft Documentation Site
latest: true
---
---
product: Release Notes
version: master
keywords: mule, 4.3.0, runtime, release notes
---

# Mule Runtime 4.3.0 Release Notes

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

Initial Release: April 30, 2020

Mule 4.3.0 includes enhancements, changes, fixes, and patch update releases. This release is also
focused on implementing several performance upgrades.

## July 2024

Patch release version: 4.3.0-20240619

This patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>The <code>mule-assembly-content-descriptor</code> file size no longer differs between <code>mule-ee-distribution-standalone</code> ZIP and Tar GZ distributions.</p></div></div></td><td><div><div><p>W-15397610</p></div></div></td></tr><tr><td><div><div><p>The redeployment of an app with a domain using a Groovy component no longer throws the <code>groovy.lang.MissingMethodException</code> exception.</p></div></div></td><td><div><div><p>W-15750766</p></div></div></td></tr><tr><td><div><div><p>DataWeave compiled expressions cache is no longer overpopulated when using nested templates.</p></div></div></td><td><div><div><p>W-15782010</p></div></div></td></tr><tr><td><div><div><p>Transactional edition and gatekeeper features are now added to version 4.3.0.</p></div></div></td><td><div><div><p>W-15641847</p></div></div></td></tr><tr><td><div><div><p>Kerberos is now enabled for proxy authentication against Anypoint Platform for Gateway capabilities.</p></div></div></td><td><div><div><p>W-15642605</p></div></div></td></tr><tr><td><div><div><p>Default stronger validations for policies are now added after applying the property <code>anypoint.platform.validate_policy_schemas</code>.</p></div></div></td><td><div><div><p>W-15769926</p></div></div></td></tr><tr><td><div><div><p>Logging for Gateway Analytics initialization is now improved.</p></div></div></td><td><div><div><p>W-15904845</p></div></div></td></tr><tr><td><div><div><p>Handling of connection errors with API platform is now improved.</p></div></div></td><td><div><div><p>W-15809377</p></div></div></td></tr><tr><td><div><div><p>Default gatekeeping for APIs that fail when doing a rollback is now added using the property <code>anypoint.platform.gatekeeper.block_failed_revert</code>.</p></div></div></td><td><div><div><p>W-15427352</p></div></div></td></tr><tr><td><div><div><p>Resiliency is now improved on policy application and updates.</p></div></div></td><td><div><div><p>W-15426528</p></div></div></td></tr></tbody></table>

There is no DataWeave update for this version.

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

## May 2024

Patch release version: 4.3.0-20240424

This patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>Jackson Databind is upgraded to version 2.13.5.</p></div></div></td><td><div><div><p>W-15427761</p></div></div></td></tr><tr><td><div><div><p><code>org.json:json</code> is upgraded to version 20231013.</p></div></div></td><td><div><div><p>W-15428060</p></div></div></td></tr><tr><td><div><div><p>Snakeyaml is upgraded to version 2.0.</p></div></div></td><td><div><div><p>W-15428154</p></div></div></td></tr><tr><td><div><div><p>Jackson dependencies are upgraded to v2.15.0 in 4.3.x.</p></div></div></td><td><div><div><p>W-15575262</p></div></div></td></tr></tbody></table>

There is no DataWeave update for this version.

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

## April 2024

Patch release version: 4.3.0-20240408

This patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>Spring is upgraded to 5.3.33.</p></div></div></td><td><div><div><p>W-15260752</p></div></div></td></tr><tr><td><div><div><p>Explicit socket connection timeout for socket creation with the management plane no longer occurs.</p></div></div></td><td><div><div><p>W-14555248</p></div></div></td></tr><tr><td><div><div><p>Template parser validation is now improved.</p></div></div></td><td><div><div><p>W-15141905</p></div></div></td></tr></tbody></table>

There is no DataWeave update for this version.

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

## November 2023

Patch release version: 4.3.0-20231026

This patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>The org.apache.santuario:xmlsec library is upgraded to 2.3.4.</p></div></div></td><td><div><div><p>W-14358602</p></div></div></td></tr><tr><td><div><div><p>Multiple redeployments of applications linked to a domain project sharing IBM MQ Connector now works as expected.</p></div></div></td><td><div><div><p>W-12388528</p></div></div></td></tr><tr><td><div><div><p><code>OutOfMemoryError</code> no longer occurs after multiple redeployments of applications with Scripting module and Groovy.</p></div></div></td><td><div><div><p>W-13038823</p></div></div></td></tr></tbody></table>

There is no DataWeave update for this version.

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

## July 2023

Patch release version: 4.3.0-20230616

This patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>Kryo is upgraded to version 4.0.3.</p></div></div></td><td><div><div><p>W-13499198</p></div></div></td></tr><tr><td><div><div><p>The <code>java.lang.NullPointerException</code> error no longer appears while refreshing an OAuth token.</p></div></div></td><td><div><div><p>W-12975498</p></div></div></td></tr></tbody></table>

There is no DataWeave update for this version.

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

## May 2023

Patch release version: 4.3.0-20230417

This patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>Added a new method for <code>CoreServiceClient</code>.</p></div></div></td><td><div><div><p>W-12659177</p></div></div></td></tr><tr><td><div><div><p>This release displays the policy definition version.</p></div></div></td><td><div><div><p>W-12733032</p></div></div></td></tr></tbody></table>

There is no DataWeave update for this version.

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

## April 2023

Patch release version: 4.3.0-20230320

This patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>Added Groovy to the default allowed scripting languages for logging.</p></div></div></td><td><div><div><p>W-12708905</p></div></div></td></tr><tr><td><div><div><p>Second Scatter Gather router does not execute when it has a Try scope for each component that raises an error handler within.</p></div></div></td><td><div><div><p>W-10619784</p></div></div></td></tr><tr><td><div><div><p>Parallel For Each gets stuck with global Error Handler operation.</p></div></div></td><td><div><div><p>W-12556497</p></div></div></td></tr><tr><td><div><div><p>Transactions in nested Try scope with global Error Handling.</p></div></div></td><td><div><div><p>W-12671732</p></div></div></td></tr><tr><td><div><div><p>Combinations of First Successful router and Raise Error component no longer causes executions to hang.</p></div></div></td><td><div><div><p>W-10619792 / MULE-19874</p></div></div></td></tr></tbody></table>

There is no DataWeave update for this version.

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

## March 2023

Patch release version: 4.3.0-20230217

This patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>DB Connector’s <code>prepareArray</code> and <code>preparaStruct</code> functions now work as expected when using them inside of a Scatter-Gather.</p></div></div></td><td><div><div><p>W-11932094</p></div></div></td></tr><tr><td><div><div><p>Requests no longer fail with <code>NullPointerException: value</code> with applications referencing a global Error Handler.</p></div></div></td><td><div><div><p>W-12535932</p></div></div></td></tr><tr><td><div><div><p>Log4j scripting now supports Nashorn languages by default.</p></div></div></td><td><div><div><p>W-12549148</p></div></div></td></tr><tr><td><div><div><p>This release updates <code>snakeyaml</code> to version 1.33.</p></div></div></td><td><div><div><p>W-12429030</p></div></div></td></tr><tr><td><div><div><p>This release updates <code>org.json:json</code> to version 20220924.</p></div></div></td><td><div><div><p>W-12450128</p></div></div></td></tr></tbody></table>

There is no DataWeave update for this version.

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

## February 2023

Patch release version: 4.3.0-20230123

This patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>Applications with an XML SDK connector now deploy correctly.</p></div></div></td><td><div><div><p>W-12362157</p></div></div></td></tr><tr><td><div><div><p>The Error Handler now contains the Event Id and Processor when handling issues from an HTTP Requester.</p></div></div></td><td><div><div><p>W-12245765</p></div></div></td></tr><tr><td><div><div><p>WSC connector with an HTTP Requester configuration no longer fails when using a domain project.</p></div></div></td><td><div><div><p>W-12407839</p></div></div></td></tr><tr><td><div><div><p>This release upgrades the <code>log4j</code> dependency to version 2.19.</p></div></div></td><td><div><div><p>W-12353442</p></div></div></td></tr><tr><td><div><div><p>This release upgrades the <code>org.apache.cxf:cxf-core</code> library to version 3.5.5.</p></div></div></td><td><div><div><p>W-12354020</p></div></div></td></tr><tr><td><div><div><p>This release upgrades the`com.hazelcast:hazelcast` dependency to version 3.12.13.</p></div></div></td><td><div><div><p>W-12354026</p></div></div></td></tr><tr><td><div><div><p>CloudHub applications no longer fail when using Global Error Handlers with a default configuration.</p></div></div></td><td><div><div><p>W-12218381</p></div></div></td></tr><tr><td><div><div><p>The insecure connection configuration in the TLS Configuration truststore now works as expected.</p></div></div></td><td><div><div><p>W-10822938</p></div></div></td></tr><tr><td><div><div><p>You can now start Mule in FIPS mode using any security provider.</p></div></div></td><td><div><div><p>W-12060316</p></div></div></td></tr></tbody></table>

There is no DataWeave update for this version.

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

## January 2023

Patch release version: 4.3.0-20221212

This patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>Distributed locks are now released properly when a policy is disabled.</p></div></div></td><td><div><div><p>W-11929632</p></div></div></td></tr><tr><td><div><div><p>The error <code>Can’t perform operation on 'Object_store'. ObjectStore not initialized</code> no longer occurs when a redelivery policy that points to an object store is declared as a top level element.</p></div></div></td><td><div><div><p>W-11985583</p></div></div></td></tr><tr><td><div><div><p>Setting a variable with a <code>null</code> value inside a Batch Aggregator component no longer fails with a <code>NullPointerException</code>.</p></div></div></td><td><div><div><p>W-11825409</p></div></div></td></tr><tr><td><div><div><p>The use of HTTP Insecure mode in a connector no longer fails with a <code>NullPointerException</code>.</p></div></div></td><td><div><div><p>W-12049036</p></div></div></td></tr><tr><td><div><div><p>The Idempotent Validation filter now cascades object store exceptions. Using the filter on Mule version 4.4 or earlier requires the property <code>mule.rethrowExceptionsInIdempotentMessageValidator=true</code>.</p></div></div></td><td><div><div><p>W-11529823</p></div></div></td></tr><tr><td><div><div><p>The XML SDK’s implicit configuration creation is disabled by default.</p></div></div></td><td><div><div><p>W-12113550</p></div></div></td></tr><tr><td><div><div><p>The Tanuki wrapper is upgraded to 3.5.51.</p></div></div></td><td><div><div><p>W-12068528</p></div></div></td></tr></tbody></table>

DataWeave 2.3.0 is bundled with the Mule 4.3.0 release. This patch release addresses the following
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>The FlatFile module now provides a reader property, <code>retainEmptyStringFieldsOnParsing</code>, for handling fields that lack values. When set to <code>true</code>, this property makes the reader retain these fields and set their values to an empty string. The default behavior of the reader is to remove those fields.</p></div></div></td><td><div><div><p>W-12036336</p></div></div></td></tr><tr><td><div><div><p>Data payloads without line breaks no longer work when using <code>lenient</code> as the <code>recordParsing</code> property. The other options to <code>recordParsing</code> support records that lack line breaks. <code>noTerminator</code> is preferred for fixed-length records that lack a line break.</p></div></div></td><td><div><div><p>W-12472890</p></div></div></td></tr></tbody></table>

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

## November 2022

> [!NOTE] November patch update 4.4.0-20221111 addresses a regression in the previous November patch
> update, 4.4.0-20221026, and includes the fixes in that patch.

### Patch 4.3.0-20221111

Patch release version: 4.3.0-20221111

This patch update addresses the following Mule issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Using the <code>insecure="true"</code> attribute of the trust-store no longer throws <code>NullPointerException</code>.</p></div></div></td><td><div><div><p>W-12049036</p></div></div></td></tr></tbody></table>

There is no DataWeave update for this version.

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

### Patch 4.3.0-20221024

Patch release version: 4.3.0-20221024

This patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><div><div><p>Applications that depend on a domain to load resources no longer fail with a <code>"Couldn’t find resource: neither on classpath or in file system"</code> error.</p></div></div></td><td><div><div><p>W-11625237</p></div></div></td></tr><tr><td><div><div><p>The <code>insecure="true"</code> attribute of the trust-store config is now honored when additional properties are defined. Use the system property <code>mule.honour.insecure.tls.configuration=true</code> to apply this behavior in Mule 4.4 or earlier.</p></div></div></td><td><div><div><p>W-10822938</p></div></div></td></tr><tr><td><div><div><p>Error mapping is no longer executed when an error occurs inside of an operation policy.</p></div></div></td><td><div><div><p>W-11861168</p></div></div></td></tr><tr><td><div><div><p>To avoid XML SDK implicit configuration creation, this release adds the system property <code>mule.disableXmlSdkImplicitConfigurationCreation=true</code>.</p></div></div></td><td><div><div><p>W-10634129</p></div></div></td></tr><tr><td><div><div><p>Transactions now honor the Transaction Timeout configured in the Try scope.</p></div></div></td><td><div><div><p>W-11741912</p></div></div></td></tr><tr><td><div><div><p>In API Gateway, SLA deletion no longer generates an inconsistent contract status.</p></div></div></td><td><div><div><p>W-11898295</p></div></div></td></tr></tbody></table>

DataWeave 2.3.0 is bundled with the Mule 4.3.0 release. This release includes only
non-user-impacting changes.

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

## October 2022

Patch release version: 4.3.0-20220922

This patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>Improved memory consumption when using global error handler.</p></div></div></td><td><div><div><p>W-11503016</p></div></div></td></tr><tr><td><div><div><p>HTTP connections no longer have a leak that prevents new connections from opening.</p></div></div></td><td><div><div><p>W-11622837</p></div></div></td></tr><tr><td><div><div><p><code>TransactionTimeout</code> is now set correctly on XA Transactions, preventing stale connections.</p></div></div></td><td><div><div><p>W-11741912</p></div></div></td></tr><tr><td><div><div><p>Improved the compatibility of SQLServer when using XA Transactions with Bitronix.</p></div></div></td><td><div><div><p>W-11228596</p></div></div></td></tr></tbody></table>

DataWeave 2.3.0 is bundled with the Mule 4.3.0 release. This patch release addresses the following
DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>The <code>Could not read from file store caused by Negative seek offset</code> error no longer occurs when transforming big XML files.</p></div></div></td><td><div><div><p>W-11620006</p></div></div></td></tr></tbody></table>

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

## September 2022

Patch release version: 4.3.0-20220824

This patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>Tanuki wrapper upgraded from 3.5.45 to 3.5.50 to support M1 (ARM) architecture.</p></div></div></td><td><div><div><p>W-11242363</p></div></div></td></tr><tr><td><div><div><p>Applications no longer fail to start with a <code>Prefix URI must be not blank</code> error.</p></div></div></td><td><div><div><p>W-11627710</p></div></div></td></tr><tr><td><div><div><p>XML SDK modules now support implicit configurations.</p></div></div></td><td><div><div><p>W-10634129</p></div></div></td></tr><tr><td><div><div><p>Log levels for successful source reconnections are now set to <code>INFO</code>.</p></div></div></td><td><div><div><p>W-11437305</p></div></div></td></tr><tr><td><div><div><p>Expired access tokens now refresh on connectors using OAuth2.</p></div></div></td><td><div><div><p>W-11535924</p></div></div></td></tr></tbody></table>

There is no DataWeave update for this version this month.

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

## August 2022

Patch release version: 4.3.0-20220725

This patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>Global Error Handler configurations no longer roll back transactions that should not roll back.</p></div></div></td><td><div><div><p>W-11324530</p></div></div></td></tr><tr><td><div><div><p>CXF is upgraded to version 3.5.1.</p></div></div></td><td><div><div><p>W-11267666</p></div></div></td></tr><tr><td><div><div><p>Mule no longer duplicates lifecycle phases for global Error Handler configurations.</p></div></div></td><td><div><div><p>W-11117613</p></div></div></td></tr><tr><td><div><div><p>Mule runtime no longer produces the following warning: <code>An expression value was given for parameter 'variableName' but it doesn’t support expressions"</code>.</p></div></div></td><td><div><div><p>W-10998630</p></div></div></td></tr><tr><td><div><div><p>Caching issues no longer cause a policy to use data from the wrong operation and produce Element and Element DSL mismatches with the flow stack.</p></div></div></td><td><div><div><p>W-11403067</p></div></div></td></tr><tr><td><div><div><p>A memory leak no longer occurs when using JMS Connector with ActiveMQ.</p></div></div></td><td><div><div><p>W-10583584</p></div></div></td></tr><tr><td><div><div><p>Error mapping now works while deploying a custom Header Injection policy.</p></div></div></td><td><div><div><p>W-11147961</p></div></div></td></tr></tbody></table>

There is no DataWeave update for this version this month.

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

## July 2022

Patch release version: 4.3.0-20220622

This patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>Spring upgraded from 5.3.18 to 5.3.21.</p></div></div></td><td><div><div><p>W-11300535</p></div></div></td></tr><tr><td><div><div><p>Jackson upgraded to 2.13.3.</p></div></div></td><td><div><div><p>W-11139348</p></div></div></td></tr></tbody></table>

DataWeave 2.3.0 is bundled with the Mule 4.3.0 release. The July patch release addresses the
following DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>This releases fixes Avro property handling.</p></div></div></td><td><div><div><p>W-11324418</p></div></div></td></tr><tr><td><div><div><p>The DataWeave Avro module now correctly converts logical types.</p></div></div></td><td><div><div><p>W-10981989/SE-16167</p></div></div></td></tr></tbody></table>

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

## June 2022

Patch release version: 4.3.0-20220523

This patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>File attributes are no longer removed when using Parallel For Each.</p></div></div></td><td><div><div><p>W-10848628</p></div></div></td></tr><tr><td><div><div><p>FIPS enabled Mule Clusters no longer throw a <code>java.nio.BufferUnderflowException</code> warning when using the RetrieveAll operation on an Object Store.</p></div></div></td><td><div><div><p>W-10884325</p></div></div></td></tr><tr><td><div><div><p>The AS400 connector now properly receives a JSON response instead of <code>org.mule.runtime.core.internal.util.message.stream.UnclosableCursorStream</code>.</p></div></div></td><td><div><div><p>W-11093225</p></div></div></td></tr><tr><td><div><div><p>Added logging to <code>AbstractQueueStoreDelegate</code> to describe why a record was not successfully queued.</p></div></div></td><td><div><div><p>W-11086587</p></div></div></td></tr><tr><td><div><div><p>Updated the error message shown when a Batch component cannot queue records.</p></div></div></td><td><div><div><p>W-11086577</p></div></div></td></tr><tr><td><div><div><p>Mule now raises an <code>ExceptionNotification</code> error when <code>ExtensionMessageSource</code> fails to start.</p></div></div></td><td><div><div><p>W-10619908</p></div></div></td></tr><tr><td><div><div><p>Mule applications no longer crash due to an unhandled <code>IllegalStateException</code> error when processing a batch block.</p></div></div></td><td><div><div><p>W-10742153</p></div></div></td></tr><tr><td><div><div><p>Mule now fails as expected if the event source configuration for the application is incorrect.</p></div></div></td><td><div><div><p>W-10619908</p></div></div></td></tr><tr><td><div><div><p>Upgraded Spring dependency from 5.1.20 to 5.3.18.</p></div></div></td><td><div><div><p>W-10989650</p></div></div></td></tr><tr><td><div><div><p>Mule application deployment properties are no longer lost after domain redeployment.</p></div></div></td><td><div><div><p>W-10984029</p></div></div></td></tr><tr><td><div><div><p>A memory leak no longer occurs after redeploying multiple times an application that uses the IBM MQ connector.</p></div></div></td><td><div><div><p>W-10672197</p></div></div></td></tr></tbody></table>

DataWeave 2.3.0 is bundled with the Mule 4.3.0 release. The June patch release addresses the
following DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>The FlatFile module now includes the <code>allowLenientWithBinaryNotEndElement</code> property to support existing behavior.</p></div></div></td><td><div><div><p>W-10935528</p></div></div></td></tr><tr><td><div><div><p>DataWeave no longer throws exceptions when using the <code>default</code> operator with <code>fromBase64</code>.</p></div></div></td><td><div><div><p>W-10648825</p></div></div></td></tr></tbody></table>

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

## April 2022

Patch release version: 4.3.0-20220321

This patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>Race conditions no longer occur when running parallel deployments.</p></div></div></td><td><div><div><p>W-10672687/SE-23764</p></div></div></td></tr><tr><td><div><div><p>Custom connector POST requests no longer send the body as NULL when handling empty payloads.</p></div></div></td><td><div><div><p>W-10818822</p></div></div></td></tr><tr><td><div><div><p>The redirect implementation properly handles the "Preserve Header Case" configuration.</p></div></div></td><td><div><div><p>W-10822777</p></div></div></td></tr></tbody></table>

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

## March 2022

Patch release version: 4.3.0-20220221

This patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>Set-Cookie is now handled correctly after a redirect request.</p></div></div></td><td><div><div><p>W-10667146 / MULE-19942</p></div></div></td></tr><tr><td><div><div><p>When disposing of an application, Mule no longer throws an <code>IOException</code> error indicating that the underlying JAR file is in use.</p></div></div></td><td><div><div><p>W-10674462 / SE-23775</p></div></div></td></tr><tr><td><div><div><p>After a failed HTTP request, applications no longer stop when reading the error payload in the error handler.</p></div></div></td><td><div><div><p>W-10681471 / MULE-19537</p></div></div></td></tr><tr><td><div><div><p><code>LifecycleObjectSorter</code> and dependency resolvers implemented in this release reduce application deployment time.</p></div></div></td><td><div><div><p>W-10745606 / W-10746226 / MULE-19984</p></div></div></td></tr><tr><td><div><div><p>Thread-local interference no longer occurs when a task is scheduled for execution on the same thread due to thread-pool exhaustion. One possible symptom was a transaction not being properly cleaned up under heavy load, followed by nested transaction errors.</p></div></div></td><td><div><div><p>W-10619599 / MULE-20072 / SE-24241</p></div></div></td></tr></tbody></table>

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

## February 2022

Patch release version: 4.3.0-20220124

This patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>Anypoint Connector for Box (Box Connector) no longer fails to recreate the input stream after an access token refresh, preventing a stream closed issue.</p></div></div></td><td><div><div><p>MULE-20001/SE-23666</p></div></div></td></tr><tr><td><div><div><p>A concurrent connection limitation in Anypoint Connector for NetSuite (NetSuite Connector) no longer occurs.</p></div></div></td><td><div><div><p>MULE-19937/SE-22359</p></div></div></td></tr><tr><td><div><div><p>The readiness check performed when deploying on Runtime Fabric is now processed correctly.</p></div></div></td><td><div><div><p>SE-22948/SE-22585</p></div></div></td></tr><tr><td><div><div><p>Running multiple MUnit cases together no longer causes a <code>No bean named '_muleDefaultObjectSerializer' available</code> error.</p></div></div></td><td><div><div><p>MULE-20012/SE-23407</p></div></div></td></tr><tr><td><div><div><p>Anypoint Connector for Google Calendar (Google Calendar Connector) no longer overwrites the access_token, which prevents generating incorrect results.</p></div></div></td><td><div><div><p>MULE-20019/SE-23584</p></div></div></td></tr><tr><td><div><div><p>Mule no longer returns an incorrect <code>CONNECTIVITY</code> error type when a <code>ConnectionException</code> is thrown when using the Java SDK.</p></div></div></td><td><div><div><p>MULE-19895/SE-24091</p></div></div></td></tr><tr><td><div><div><p>Mule no longer performs a thread switch in a transactional context that uses multithread and the same <code>cache-key</code>.</p></div></div></td><td><div><div><p>EE-8216/SE-23816</p></div></div></td></tr><tr><td><div><div><p>Global property values of a module are now accessible within a private operation that is invoked within a flow control component.</p></div></div></td><td><div><div><p>MULE-19962/MULE-19035/SE-22282</p></div></div></td></tr></tbody></table>

DataWeave 2.3.0 is bundled with the Mule 4.3.0 release. The February patch release addresses the
following DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>Corrected the documentation for the <code>Periods::between</code> function.</p></div></div></td><td><div><div><p>DW-1070</p></div></div></td></tr><tr><td><div><div><p>Upgraded the <code>edi-parser</code> with SLF4J.</p></div></div></td><td><div><div><p>CONN-9598</p></div></div></td></tr></tbody></table>

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

## January 2022

Patch release version: 4.3.0-20211222

This patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>The <code>FlowProcessMediator</code> no longer leaks the payload of the first request.</p></div></div></td><td><div><div><p>MULE-19869</p></div></div></td></tr><tr><td><div><div><p>If the redelivery policy is exhausted in a source configured with transactions, Mule no longer raises an error that runs in a loop.</p></div></div></td><td><div><div><p>MULE-19915</p></div></div></td></tr><tr><td><div><div><p>Processors in subflows now get the processing strategy of the root flow.</p></div></div></td><td><div><div><p>MULE-19924</p></div></div></td></tr><tr><td><div><div><p>MUnit tests now initialize object stores inside redelivery policies.</p></div></div></td><td><div><div><p>MULE-19928/SE-20765</p></div></div></td></tr><tr><td><div><div><p>Autogenerated Mule connectors no longer fail with <code>NumberFormatException</code> errors.</p></div></div></td><td><div><div><p>MULE-19871/SE-21463</p></div></div></td></tr><tr><td><div><div><p>Applications that implement a VM Listener source no longer raise <code>java.lang.IllegalStateException: No connection has been bound</code> errors and quit.</p></div></div></td><td><div><div><p>SE-22172</p></div></div></td></tr><tr><td><div><div><p>This releases fixes performance issues with the Web Service Consumer connector when deployed in CloudHub.</p></div></div></td><td><div><div><p>SE-22245</p></div></div></td></tr><tr><td><div><div><p>You can now redeploy applications that were in a stopped state when they were deleted.</p></div></div></td><td><div><div><p>MULE-19890/SE-22261</p></div></div></td></tr><tr><td><div><div><p>DataWeave now escapes the <code>\</code> symbol when used in combination with the <code>"</code> symbol.</p></div></div></td><td><div><div><p>MULE-19900/SE-22346</p></div></div></td></tr><tr><td><div><div><p>The batch processing On Complete phase no longer fails if it encounters an error stream.</p></div></div></td><td><div><div><p>EE-8020/SE-22386</p></div></div></td></tr><tr><td><div><div><p>Logs no longer show reconnection successful messages when reconnection attempts to the FTP server are exhausted because the server is unavailable.</p></div></div></td><td><div><div><p>SE-22434</p></div></div></td></tr><tr><td><div><div><p>Transactions opened by the JMS Listener are no longer rolled back.</p></div></div></td><td><div><div><p>MULE-19919/SE-23039</p></div></div></td></tr><tr><td><div><div><p>You can now perform parallel deployments of apps that are linked to a domain and share a configuration.</p></div></div></td><td><div><div><p>MULE-19912/SE-23123</p></div></div></td></tr><tr><td><div><div><p>Mule now recognizes Eclipse Temurin by Adoptium (formerly Adopt OpenJDK project) as a recommended JDK Vendor and no longer raises an INFO-level log message.</p></div></div></td><td><div><div><p>MULE-19917/SE-23354</p></div></div></td></tr><tr><td><div><div><p>Apache Commons Compress upgraded to version 1.21.</p></div></div></td><td><div><div><p>EE-8088</p></div></div></td></tr><tr><td><div><div><p>GSON upgraded to version 2.8.9.</p></div></div></td><td><div><div><p>EE-8154</p></div></div></td></tr><tr><td><div><div><p>When a source is configured to use transactions, and the message ID for the redelivery policy is blank or null, the source no longer fails to find the redelivery attempts counter.</p></div></div></td><td><div><div><p>MULE-19921</p></div></div></td></tr><tr><td><div><div><p>You can now use the inline string array parameter on operations defined with the Mule XML SDK.</p></div></div></td><td><div><div><p>MULE-19853</p></div></div></td></tr><tr><td><div><div><p>Kryo updated to version 4.0.2.</p></div></div></td><td><div><div><p>EE-8153</p></div></div></td></tr><tr><td><div><div><p>Apache Velocity updated.</p></div></div></td><td><div><div><p>EE-8010</p></div></div></td></tr><tr><td><div><div><p>MUnit no longer fails with a <code>RejectedExecutionException</code> error.</p></div></div></td><td><div><div><p>SE-22728</p></div></div></td></tr><tr><td><div><div><p>Scheduler runs using cron expressions are no longer rejected if other scheduler components are under back pressure.</p></div></div></td><td><div><div><p>SE-22941</p></div></div></td></tr><tr><td><div><div><p>An issue that caused a <code>No qualifying bean of type 'org.mule.extensions.java.internal.cache.JavaModuleLoadingCache' available</code> error no longer occurs.</p></div></div></td><td><div><div><p>MULE-19896/SE-23142</p></div></div></td></tr><tr><td><div><div><p>A performance degradation related to processing parallel requests for applications deployed to the latest Mule runtime version in Runtime Fabric no longer occurs.</p></div></div></td><td><div><div><p>EE-8150/SE-23510</p></div></div></td></tr><tr><td><div><div><p>The JMS Connector no longer leaks connections and now honors connection pools in XA mode with Solace JMS.</p></div></div></td><td><div><div><p>MULE-19848/SE-22284</p></div></div></td></tr></tbody></table>

DataWeave 2.3.0 is bundled with the Mule 4.3.0 release. The January patch release addresses the
following DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>DataWeave now shows the root cause of an error when an exception occurs while reading an input.</p></div></div></td><td><div><div><p>SE-22939</p></div></div></td></tr><tr><td><div><div><p>This release resolves an <code>OutOfMemory</code> error when using the <code>writeLinesWith</code> function, which affected the <code>ndjson</code> module.</p></div></div></td><td><div><div><p>SE-23759</p></div></div></td></tr></tbody></table>

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

## November 2021

> [!NOTE] November patch update 4.3.0-20211104 addresses a regression in the previous November patch
> update, 4.3.0-20211026, and includes the fixes in that patch.
>
> - If you installed the previous November patch, 4.3.0-20211026, install patch 4.3.0-20211104 to
>   address the regression.
>
> - If you did _not_ install the previous November patch, 4.3.0-20211026, skip that patch, and
>   install the new patch, 4.3.0-20211104.

### Patch 4.3.0-20211104

Patch release version: 4.3.0-20211104

This November update addresses a regression introduced in the previous November patch,
4.3.0-20211026:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p><code>QueryParams</code> are no longer lost when HTTP redirects take place.</p></div></div></td><td><div><div><p>MULE-19811</p></div></div></td></tr><tr><td><div><div><p>Addressed a regression in the initial November patch update.</p></div></div></td><td><div><div><p>SE-23349</p></div></div></td></tr></tbody></table>

### Patch 4.3.0-20211026

Patch release version: 4.3.0-20211026

> [!NOTE] Skip this patch, and install a later patch. Fixes in this patch are included in later
> patches.

This November patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>The <code>CachedConnectionProvider</code> no longer returns the same connection to a source if <code>sourceCallback.onConnectionException(e)</code> is called.</p></div></div></td><td><div><div><p>MULE-19678/SE-21176</p></div></div></td></tr><tr><td><div><div><p>Fixed <code>NullPointerException</code> handling when serializing or transforming Mule errors from the Until Successful component.</p></div></div></td><td><div><div><p>MULE-19811/SE-20502</p></div></div></td></tr><tr><td><div><div><p>Fixed a <code>ClassCastException</code> that occurred in the Avro module by correcting its generated MIME type.</p></div></div></td><td><div><div><p>SE-21869</p></div></div></td></tr><tr><td><div><div><p>An issue with nesting referenced Flow Reference components no longer occurs.</p></div></div></td><td><div><div><p>MULE-19831/SE-22539</p></div></div></td></tr><tr><td><div><div><p>Fixed a memory leak in <code>org.mule.runtime.core.internal.rx.FluxSinkRecorder</code>.</p></div></div></td><td><div><div><p>MULE-19846/SE-22780</p></div></div></td></tr><tr><td><div><div><p>Applications now start correctly after the September patch update is applied.</p></div></div></td><td><div><div><p>MULE-19815/SE-22845</p></div></div></td></tr><tr><td><div><div><p>Caffeine cache now correctly processes large payloads with a VM queue.</p></div></div></td><td><div><div><p>MULE-19869/SE-22773</p></div></div></td></tr><tr><td><div><div><p>The Scheduler component no longer causes intermittent deployment failures.</p></div></div></td><td><div><div><p>MULE-19774/SE-22851</p></div></div></td></tr><tr><td><div><div><p>Mule now handles concurrent requests correctly when a Mule application makes an HTTP request that returns a 301 redirect.</p></div></div></td><td><div><div><p>SE-22922/SE-19944</p></div></div></td></tr></tbody></table>

DataWeave 2.3.0 is bundled with the Mule 4.3.0 release. The November patch release addresses the
following DataWeave issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>Fixed a <code>ClassCastException</code> that occurred in the Avro module by correcting its generated MIME type.</p></div></div></td><td><div><div><p>SE-21869</p></div></div></td></tr></tbody></table>

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

## October 2021

Patch release version: 4.3.0-20210915

To include updated patching instructions, the patch update for the standalone version of Mule was
republished as `mule-ee-patch-4.3.0-20210915-HF1-OCTOBER.zip` in your customer portal.

The October patch update addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Description</th><th>Issue</th></tr></thead><tbody><tr><td><div><div><p>Metadata now resolves correctly for components with multi-level keys.</p></div></div></td><td><div><div><p>MULE-19740/SE-22356</p></div></div></td></tr><tr><td><div><div><p>When using the <code>#[flow.name]</code> value in a Set Variable component, Mule now correctly recognizes <code>flow.name</code>.</p></div></div></td><td><div><div><p>MULE-19732/SE-20384</p></div></div></td></tr><tr><td><div><div><p>Applications now continue correctly when a dynamic flow reference resolves to non-existent flow.</p></div></div></td><td><div><div><p>MULE-19742/SE-20838</p></div></div></td></tr><tr><td><div><div><p>Mule runtime engine no longer stops accepting requests after a <code>No listener</code> error occurs.</p></div></div></td><td><div><div><p>MULE-19533/SE-20958/SE-21576</p></div></div></td></tr><tr><td><div><div><p>Applications that include the Dynamic Evaluate component in a sub-flow now deploy correctly.</p></div></div></td><td><div><div><p>EE-8018/SE-21777</p></div></div></td></tr><tr><td><div><div><p>Introduced a new mechanism for collecting API gateway usage statistics, which defaults to enabled.</p></div><div><p>To opt out, include <code>anypoint.platform.metrics_enabled=false</code> in <code>wrapper.conf</code> or as a parameter when starting Mule.</p></div></div></td><td><div><div><p>AGW-4823</p></div></div></td></tr></tbody></table>

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

## September 2021

Patch release version: 4.3.0-20210823

The September patch update adddresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>MULE-19707/SE-22200</p></div></div></td><td><div><div><p>Fixed an issue that caused some applications and connectors to become unresponsive due to a <code>NullPointerException</code> error.</p></div></div></td></tr><tr><td><div><div><p>MULE-19620/SE-21555</p></div></div></td><td><div><div><p>Applications now properly release resources allocated by the IBM MQ connector when the application stops.</p></div></div></td></tr><tr><td><div><div><p>MULE-19699/SE-21576</p></div></div></td><td><div><div><p>Fixed a race condition occuring during parallel deployments that caused deployments to fail.</p></div></div></td></tr><tr><td><div><div><p>MULE-19684/SE-22043</p></div></div></td><td><div><div><p>Fixed a default error handling issue in the error handler.</p></div></div></td></tr><tr><td><div><div><p>MULE-19680/SE-22129</p></div></div></td><td><div><div><p>Mule now masks sensitive data and secure properties (e.g. master password) in logs and UI.</p></div></div></td></tr><tr><td><div><div><p>MULE-19498</p></div></div></td><td><div><div><p>SDK: The <code>@Export</code> annotation now works with the Enum type.</p></div></div></td></tr><tr><td><div><div><p>MULE-19624/SE-21593</p></div></div></td><td><div><div><p>Restarting an on-premises Mule application with flows with <code>initialState=stopped</code> no longer leaks memory.</p></div></div></td></tr><tr><td><div><div><p>SE-21685/EE-7995</p></div></div></td><td><div><div><p>Fixed error conditions and messages for MUnit tests.</p></div></div></td></tr><tr><td><div><div><p>MULE-19562 /SE-21626</p></div></div></td><td><div><div><p>Fixed <code>NullPointerException</code> errors on nested VM Transactions.</p></div></div></td></tr><tr><td><div><div><p>MULE-19691/SE-21658</p></div></div></td><td><div><div><p>Closing the connection now works correctly if a timeout occurs when an empty payload is sent.</p></div></div></td></tr><tr><td><div><div><p>MULE-19622/SE-19944</p></div></div></td><td><div><div><p>When handling redirect responses, Mule no longer becomes unresponsive.</p></div></div></td></tr><tr><td><div><div><p>SE-21417</p></div></div></td><td><div><div><p>DataWeave Flatfile: Added the reader and writer property <code>useMissCharAsDefaultForFill</code> for the flat file format. When this property is set to <code>true</code>, DataWeave uses the fill character configured in the <code>missingValues</code> property to trim or pad elements. If <code>useMissCharAsDefaultForFill</code> is set to <code>false</code>, DataWeave uses the space character.</p></div></div></td></tr><tr><td><div><div><p>SE-22171</p></div></div></td><td><div><div><p>DataWeave: The <code>distinctBy</code> function now works as expected when used with <code>mapObject</code> or <code>filter</code>.</p></div></div></td></tr><tr><td><div><div><p>SE-21050</p></div></div></td><td><div><div><p>DataWeave: Fixed an issue that showed an internal exception instead of the expected <code>InvalidUrlEncodingException</code> error message.</p></div></div></td></tr></tbody></table>

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

## August 2021

Patch release version: 4.3.0-20210719

The August patch update adddresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>MULE-19586/SE-21826</p></div></div></td><td><div><div><p>Introduces a <code>mule.setVariable.WithNullValue=true</code> property for the Set Variable component, which enables you to create a Mule variable with a <code>null</code> value. In Mule 4.4, this behavior will be the default.</p></div></div></td></tr><tr><td><div><div><p>MULE-19485/SE-21019</p></div></div></td><td><div><div><p>Incorrect status codes and error descriptions no longer occur when using policies.</p></div></div></td></tr><tr><td><div><div><p>EE-7907/SE-20588</p></div></div></td><td><div><div><p>Improves the handling of XA transactions when using Anypoint Connector for IBM MQ by fixing the error <code>bitronix.tm.internal.BitronixSystemException - cannot delist an XAResourceHolderState</code>.</p></div></div></td></tr><tr><td><div><div><p>EE-7890/SE-20153</p></div></div></td><td><div><div><p>Errors from a Batch Aggregator scope are now available within the Batch Step that handles errors.</p></div></div></td></tr><tr><td><div><div><p>SE-21198</p></div></div></td><td><div><div><p>DataWeave: Introduces a reader property (<code>defaultContentType</code>) and a system property (<code>com.mulesoft.dw.multipart.defaultContentType</code>) to change the default Content-Type for multipart parts.</p></div></div></td></tr><tr><td><div><div><p>SE-21632</p></div></div></td><td><div><div><p>DataWeave: Temporary files created during the Excel streaming process are now deleted.</p></div></div></td></tr><tr><td><div><div><p>SE-21585</p></div></div></td><td><div><div><p>DataWeave: Addresses the presence of big objects that are pending finalization.</p></div></div></td></tr><tr><td><div><div><p>SE-21873</p></div></div></td><td><div><div><p>DataWeave FlatFile: Fixes end-of-input data detection when Copybook structures have multiple segments with repeated composite and element components.</p></div></div></td></tr></tbody></table>

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

## July 2021

Patch release version: 4.3.0-20210622

The July patch update adddresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>MULE-19226/SE-16379</p></div></div></td><td><div><div><p>When deploying policies that use extensions (such as connectors) that are also used in the target application, <code>NoSuchBeanDefinitionException</code> errors are no longer thrown.</p></div></div></td></tr><tr><td><div><div><p>MULE-19512/SE-20259</p></div></div></td><td><div><div><p>The Anypoint Studio 7.8 debugger no longer stops working unexpectedly when an error occurs in the flow execution.</p></div></div></td></tr><tr><td><div><div><p>MULE-19471/SE-20711</p></div></div></td><td><div><div><p>The <code>Propagating completion</code> default log level changed from <code>WARN</code> to <code>DEBUG</code>.</p></div></div></td></tr><tr><td><div><div><p>MULE-19431</p></div></div></td><td><div><div><p>If they are in the same scope or in a nested scope, you can now properly chain transaction interceptors that have different <code>transactionalAction</code> values.</p></div></div></td></tr><tr><td><div><div><p>MULE-19290</p></div></div></td><td><div><div><p>The initialization policy for pooling profiles now honors the selected option, and no longer initializes to <code>none</code> in all cases.</p></div></div></td></tr><tr><td><div><div><p>MULE-19430/SE-20576</p></div></div></td><td><div><div><p>Two or more nested XA (Extended Architecture) transactions no longer fail with <code>NullPointerException</code> errors.</p></div></div></td></tr><tr><td><div><div><p>MULE-19443/SE-20938</p></div></div></td><td><div><div><p>The Set Variable component now creates a variable when the value is <code>null</code>.</p></div></div></td></tr><tr><td><div><div><p>SE-20940</p></div></div></td><td><div><div><p>The contracts database for API Gateway now self-recovers after experiencing a <code>Wrong index checksum</code> or other errors.</p></div></div></td></tr><tr><td><div><div><p>MULE-19418/SE-20254</p></div></div></td><td><div><div><p>When the Anypoint Connector for AMQP (AMQP Connector) experiences connectivity errors, transactions are now rolled back, as expected.</p></div></div></td></tr><tr><td><div><div><p>SE-19983</p></div></div></td><td><div><div><p>DataWeave has improved error reporting for recursive imports.</p></div></div></td></tr><tr><td><div><div><p>SE-21133</p></div></div></td><td><div><div><p>DataWeave <code>0x025</code>(LF) byte conversion for IBM037 encoding now works as expected.</p></div></div></td></tr><tr><td><div><div><p>SE-20880</p></div></div></td><td><div><div><p>DataWeave flat files now contain the property <code>notTruncateDependingOnSubjectNotPresent</code> to avoid truncating the group-item when the subject is not present or the length of the subject of an <code>OCCURS</code> clause is zero. Earlier versions contained this property.</p></div></div></td></tr><tr><td><div><div><p>SE-20878</p></div></div></td><td><div><div><p>DataWeave no longer raises <code>Negative Index Exception</code> errors when processing JSON files over 10 GB.</p></div></div></td></tr><tr><td><div><div><p>MULE-19442</p></div></div></td><td><div><div><p>Input stream parameters on a Parameter Group with <code>showInDsl=true</code> now resets after refreshing an expired OAuth token.</p></div></div></td></tr><tr><td><div><div><p>MULE-19426/SE-20477</p></div></div></td><td><div><div><p>Anypoint MQ connectors are now available in flows after non-transactional MQ publish operations to preserve backwards compatible behavior with Mule 4.2.</p></div></div></td></tr></tbody></table>

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

## June 2021

The following notification applies to each patch release in June.

> [!NOTE] The default for the DataWeave XML reader property `supportDtd` changes to `false` in this
> release. The new default is described in fixed issue DW-377.
>
> This change affects Mule versions 4.3.0 for on-premises Mule, CloudHub, and other hosted or
> embedded runtimes, including Anypoint Runtime Fabric and Anypoint Studio. Future patches to these
> releases and future minor releases of Mule will also incorporate the new default.

The June update 4.3.0-20210609 addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>SE-20497</p></div></div></td><td><div><div><p>DataWeave: A <code>StackOverflow</code> error no longer occurs when concatenating arrays.</p></div></div></td></tr><tr><td><div><div><p>SE-20846</p></div></div></td><td><div><div><p>DataWeave: Applications that use multiple <code>++</code> operators no longer fail to deploy.</p></div></div></td></tr></tbody></table>

The June update 4.3.0-20210601 addresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>MULE-19282/SE-17938</p></div></div></td><td><div><div><p>Deployments now take into account Maven profiles defined in the <code>pom.xml</code> file, preventing errors due to dependencies not loaded correctly, such as <code>Cannot load class oracle.jdbc.driver.OracleDriver</code>.</p></div></div></td></tr><tr><td><div><div><p>MULE-19328/SE-19407</p></div></div></td><td><div><div><p><code>EVENTS_ACCUMULATED</code> error no longer occur after an application restart that caused app’s schedulers to stop working.</p></div></div></td></tr><tr><td><div><div><p>MULE-19319</p></div></div></td><td><div><div><p>A For Each scope that points to a Flow Reference component using <code>max-concurrency</code> no longer gets stuckt.</p></div></div></td></tr><tr><td><div><div><p>MULE-19315/SE-19762</p></div></div></td><td><div><div><p>The connector Reconnection Strategy is now correctly honored when running in debugging mode.</p></div></div></td></tr><tr><td><div><div><p>MULE-19220/SE-19580</p></div></div></td><td><div><div><p>Logging context entries are now propagated correctly to asynchronous SDK operations.</p></div></div></td></tr><tr><td><div><div><p>MULE-19297/SE-19166</p></div></div></td><td><div><div><p>Streams are no longer closed when consumed inside of a scope.</p></div></div></td></tr><tr><td><div><div><p>MULE-19279/SE-15347</p></div></div></td><td><div><div><p>Binary payloads are no longer corrupted when using VM queues.</p></div></div></td></tr><tr><td><div><div><p>MULE-19289</p></div></div></td><td><div><div><p>Logging now includes the original exception when managing reconnection scenarios.</p></div></div></td></tr><tr><td><div><div><p>MULE-19291/SE-20299</p></div></div></td><td><div><div><p>The timestamp reported by XA Bitronix Transaction is now output correctly.</p></div></div></td></tr><tr><td><div><div><p>MULE-19406</p></div></div></td><td><div><div><p>The system property name <code>mule..enableStreamingStatistics</code> was corrected to <code>mule.enableStreamingStatistics</code>.</p></div></div></td></tr><tr><td><div><div><p>MULE-19342/SE-20247</p></div></div></td><td><div><div><p>Scheduler jobs no longer get stuck due to a race condition.</p></div></div></td></tr><tr><td><div><div><p>SE-20356</p></div></div></td><td><div><div><p>Connection pool now behaves as expected when using a reconnection strategy or using <code>#[]</code> expressions in the connector <code>config</code> element.</p></div></div></td></tr><tr><td><div><div><p>MULE-19356/SE-20465</p></div></div></td><td><div><div><p>Mule runtime engine no longer shuts down with a <code>NullPointerException</code> error when encountering flows without sources.</p></div></div></td></tr><tr><td><div><div><p>MULE-19390/SE-20448</p></div></div></td><td><div><div><p>Using a <code>@ParameterGroup</code> annotation with an <code>@ExclusiveOptionals</code> annotation that references another parameter with the same name outside the group no longer causes the deployment to fail with the error <code>the following parameters cannot be set at the same time</code>.</p></div></div></td></tr><tr><td><div><div><p>MULE-19408/SE-20491</p></div></div></td><td><div><div><p>Error propagation with certain error types when using Mule runtime cluster now works correctly.</p></div></div></td></tr><tr><td><div><div><p>MULE-19409</p></div></div></td><td><div><div><p>The logs now include JAR files added to the class loader to facilitate troubleshooting server-plugin class loader creation.</p></div></div></td></tr><tr><td><div><div><p>MULE-19371/MULE-19370/SE-20386</p></div></div></td><td><div><div><p><code>TieredCompilation</code> no longer prevents apps from working on 0.1 vCore when deployed on a worker with a higher vCore, such as 0.2 vCore.</p></div></div></td></tr><tr><td><div><div><p>MULE-19387/SE-20319</p></div></div></td><td><div><div><p>Using the Java Module in a policy no longer prevents the policy from deploying successfully.</p></div></div></td></tr><tr><td><div><div><p>MULE-19240/SE-20745</p></div></div></td><td><div><div><p>Deploying a custom policy on Windows no longer fails if the log file name contains <code>:</code> characters.</p></div></div></td></tr><tr><td><div><div><p>MULE-18580</p></div></div></td><td><div><div><p>Setting a Date with Time and TimeZone precision from a String value now works correctly without requiring a DataWeave expression. In addition, setting time-based parameters following the ISO-8601 standard is now supported.</p></div></div></td></tr><tr><td><div><div><p>MULE-19347/SE-19450</p></div></div></td><td><div><div><p>Anypoint Connector for JMS (Java Message Service) using XA Transactions with Bitronix now honors the reconnection strategy.</p></div></div></td></tr><tr><td><div><div><p>MULE-19010</p></div></div></td><td><div><div><p>Using the Scatter-Gather component with the Flow Reference component no longer causes <code>MULE:UNKNOWN</code> errors.</p></div></div></td></tr><tr><td><div><div><p>SE-20417</p></div></div></td><td><div><div><p>The logs now include only one <code>Back Pressure</code> error per exception.</p></div></div></td></tr><tr><td><div><div><p>SE-20952</p></div></div></td><td><div><div><p>Corrected information in the <code>mule-ee-patch-4.3.0-20210427-MAY-2021.zip</code> README.TXT file.</p></div></div></td></tr><tr><td><div><div><p>EE-6454</p></div></div></td><td><div><div><p>The Transform Message component now loads resources using the correct encoding.</p></div></div></td></tr><tr><td><div><div><p>EE-7739/SE-19692</p></div></div></td><td><div><div><p>Undeploying applications in a cluster with FIPS enabled no longer causes the process to hang.</p></div></div></td></tr><tr><td><div><div><p>EE-7524</p></div></div></td><td><div><div><p>The Cache Scope component no longer creates incompatible cache values during Mule runtime engine upgrades.</p></div></div></td></tr><tr><td><div><div><p>EE-7284</p></div></div></td><td><div><div><p>Clusters configured to use encrypted communication now work as expected.</p></div></div></td></tr><tr><td><div><div><p>AGW-4731</p></div></div></td><td><div><div><p>Closed sockets are now recovered correctly when an unexpected platform connection error occurs.</p></div></div></td></tr><tr><td><div><div><p>AGW-4747/SE-19546</p></div></div></td><td><div><div><p>The client secret of client credentials can now be hashed when storing the credentials in memory and when parsing incoming credentials from a request.</p></div><div><p>This functionality is disabled by default.</p></div></div></td></tr><tr><td><div><div><p>AGW-4797</p></div></div></td><td><div><div><p>Removed unused Jersey dependencies.</p></div></div></td></tr><tr><td><div><div><p>DW-377</p></div></div></td><td><div><div><p>DataWeave: Support for XML DTD validation is now disabled by default.</p></div><div><p>To enable XML DTD validation, use the <code>com.mulesoft.dw.xml.supportDTD</code> system property or the <code>supportDtd</code> XML reader property.</p></div></div></td></tr><tr><td><div><div><p>SE-19933</p></div></div></td><td><div><div><p>Schedule-based flows no longer stall after the first batch is processed when the value of <code>maxConcurrency</code> is 1.</p></div></div></td></tr><tr><td><div><div><p>SE-20129</p></div></div></td><td><div><div><p>DataWeave: The character reader property now correctly handles <code>null</code> as an empty value.</p></div></div></td></tr><tr><td><div><div><p>SE-20300</p></div></div></td><td><div><div><p>DataWeave: An <code>OutOfMemory</code> error no longer occurs when using MultiPart format.</p></div></div></td></tr><tr><td><div><div><p>SE-20372</p></div></div></td><td><div><div><p>DataWeave: A <code>StackOverflow</code> error no longer occurs when using <code>StreamCapable</code> check-recursive functions.</p></div></div></td></tr><tr><td><div><div><p>SE-16906</p></div></div></td><td><div><div><p>Event variables that are visible in a Try scope are now visible inside error handlers.</p></div></div></td></tr></tbody></table>

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

## April 2021

Patch release version: 4.3.0-20210322

> [!NOTE] For an upcoming release in May, the behavior of the DataWeave XML reader functionality
> will change.
>
> This change will affect Mule versions 3.9.5, 4.1.6, 4.2.2, and 4.3.0 for on-premises Mule,
> CloudHub, and other hosted or embedded runtimes, including Anypoint Runtime Fabric and Anypoint
> Studio.

The April patch update adddresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>SE-20108</p></div></div></td><td><div><div><p>Fixed a known issue that could cause a <code>com.esotericsoftware.kryo.KryoException: Buffer underflow</code> error to occur in CloudHub when using Object Store v2 after updating to the March 2021 release.</p></div></div></td></tr><tr><td><div><div><p>MULE-19272/SE-18122</p></div></div></td><td><div><div><p>Fixed the error <code>Couldn’t find resource: script.dwl neither on classpath or in file system</code>, which occurred when using the Transform Message component (<code>ee:transform</code>) in a subflow called from Parallel For Each (<code>parallel-foreach</code>), Scatter-Gather (<code>scatter-gather</code>), or Cache <code>ee:cache</code> components.</p></div></div></td></tr><tr><td><div><div><p>MULE-19262</p></div></div></td><td><div><div><p>Fixed an issue that occurred when retrying an operation after refreshing an OAuth token. Consumable values (such as streams) of parameters in the operation were already consumed and not reset upon retrying the operation.</p></div></div></td></tr><tr><td><div><div><p>MULE-19252</p></div></div></td><td><div><div><p>Improved the performance of persistent object stores.</p></div></div></td></tr><tr><td><div><div><p>MULE-19249/SE-19746</p></div></div></td><td><div><div><p>Fixed an issue that caused errors when referencing files on a network share path in a Windows environment.</p></div></div></td></tr><tr><td><div><div><p>MULE-19076</p></div></div></td><td><div><div><p>Fixed the log message for <code>org.mule.runtime.core.internal.processor.simple.RemoveFlowVariableProcessor</code>.</p></div></div></td></tr><tr><td><div><div><p>EE-7703/SE-16631/SE-17432</p></div></div></td><td><div><div><p>Fixed an issue that occurred when using XA transactions in the Anypoint Connector for Database (Database Connector).</p></div><div><p>The application did not resolve metadata correctly and failed when testing with MUnit.</p></div></div></td></tr><tr><td><div><div><p>MULE-19242/SE-18799</p></div></div></td><td><div><div><p>Fixed a file leak on Windows that prevented Mule from deleting the application’s folder when redeploying, which caused a failure.</p></div></div></td></tr><tr><td><div><div><p>SE-19846</p></div></div></td><td><div><div><p>DataWeave: To fix an <code>OutOfMemory</code> error that occurred when mapping many database records, DataWeave now releases resources on stream close.</p></div></div></td></tr><tr><td><div><div><p>SE-19257</p></div></div></td><td><div><div><p>DataWeave: Fixed flat file handling of records with values of variable length.</p></div></div></td></tr><tr><td><div><div><p>SE-20005</p></div></div></td><td><div><div><p>DataWeave: Increased the number of namespaces that can be handled by the XML module to avoid <code>NoSuchElementException</code> errors.</p></div></div></td></tr></tbody></table>

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

## March 2021

Patch release version: 4.3.0-20210304

Known Issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>SE-20108</p></div></div></td><td><div><div><p>The Cache scope can fail when using a persistent Mule object store or Object Store v2 after upgrading to the March 2021 patch release for 4.3.0 from an older version.</p></div></div></td></tr></tbody></table>

The March patch update adddresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>MULE-19127</p></div></div></td><td><div><div><p>Added the ability to redeploy a flow without starting it to enable the server to restart without starting the applications.</p></div></div></td></tr><tr><td><div><div><p>AGW-4551</p></div></div></td><td><div><div><p>Enhanced <code>org.mule.runtime.api.healthcheck.ReadyStatus</code> to provide more information.</p></div></div></td></tr><tr><td><div><div><p>AGW-4650</p></div></div></td><td><div><div><p>Fixed a problem in which removing a policy with contracts before the contracts were downloaded caused the gatekeeper to remain locked.</p></div></div></td></tr><tr><td><div><div><p>AGW-4619</p></div></div></td><td><div><div><p>Gatekeeper now waits for contracts to download.</p></div></div></td></tr><tr><td><div><div><p>DW-375</p></div></div></td><td><div><div><p>DataWeave: Prevented an overflow exception by getting a binary token offset.</p></div></div></td></tr><tr><td><div><div><p>SE-11046</p></div></div></td><td><div><div><p>Resolved an issue in which MUnit couldn’t run from behind an authenticated a Nexus repository.</p></div></div></td></tr><tr><td><div><div><p>SE-16673/EE-7664</p></div></div></td><td><div><div><p>Resolved a problem using Bitronix TM that caused the application to fail when the database was not reachable.</p></div></div></td></tr><tr><td><div><div><p>SE-19030/EE-7653</p></div></div></td><td><div><div><p>Fixed a problem that prevented XA MQ connections from committing if the flow used a cache element.</p></div></div></td></tr><tr><td><div><div><p>SE-18881/EE-7654</p></div></div></td><td><div><div><p>Fixed a validation issue that prevented setting <code>preparedStatementCacheSize</code> to <code>0</code>.</p></div></div></td></tr><tr><td><div><div><p>SE-19090</p></div></div></td><td><div><div><p>DataWeave: Changed local imported modules to be cached to avoid <code>CompilationResult</code> class leaks.</p></div></div></td></tr><tr><td><div><div><p>SE-19157</p></div></div></td><td><div><div><p>DataWeave: Fixed an issue in which the splitter generated the wrong exception and caused Scala serialization issues.</p></div></div></td></tr><tr><td><div><div><p>SE-19266</p></div></div></td><td><div><div><p>DataWeave: Updated to use encoding when converting a string to a byte array.</p></div></div></td></tr><tr><td><div><div><p>SE-19442</p></div></div></td><td><div><div><p>DataWeave: Fixed an issue in which the pattern matcher didn’t work with comments, causing the script to fail.</p></div></div></td></tr><tr><td><div><div><p>MULE-19139</p></div></div></td><td><div><div><p>Fixed an issue in which mapped errors threw a <code>MULE:UNKNOWN</code> error, instead of the correct error name.</p></div></div></td></tr><tr><td><div><div><p>MULE-18663</p></div></div></td><td><div><div><p>When annotating parameters from OAuth-based connection providers with <code>@OAuthParameter</code> and <code>requestAlias</code>, the value of the parameter is now correctly sent when performing the OAuth dance.</p></div></div></td></tr><tr><td><div><div><p>MULE-19020</p></div></div></td><td><div><div><p>Fixed an issue in which connection errors were not computed in application error-count statistics.</p></div></div></td></tr><tr><td><div><div><p>MULE-19143</p></div></div></td><td><div><div><p>Fixed an issue that caused a <code>NullPointerException</code> error while using Parallel For Each combined with a For Each under high concurrency.</p></div></div></td></tr><tr><td><div><div><p>MULE-19160</p></div></div></td><td><div><div><p>Resolved a problem in which retrying policies for operations did not correctly override connection-provider policies.</p></div></div></td></tr><tr><td><div><div><p>MULE-19209/SE-19515</p></div></div></td><td><div><div><p>Fixed an issue in which a cache held a reference to a thread and a stream, which might cause high memory consumption.</p></div></div></td></tr><tr><td><div><div><p>MULE-19219</p></div></div></td><td><div><div><p>Fixed an issue in which <code>MediaType</code> did not correctly escape characters.</p></div></div></td></tr><tr><td><div><div><p>SE-16747</p></div></div></td><td><div><div><p>Resolved an issue that occurred when using the <code>validation:all</code> scope and a <code>validation:is-not-null</code> operation was triggered, the other items in the For Each weren’t processed.</p></div></div></td></tr><tr><td><div><div><p>SE-19213</p></div></div></td><td><div><div><p>Fixed a <code>NullPointerException</code> error that occurred while processing, under high concurrency, a Parallel For Each with either <code>max-concurrency</code> set to a value other than <code>1</code> or not set.</p></div></div></td></tr><tr><td><div><div><p>SE-19136</p></div></div></td><td><div><div><p>Resolved a problem in which the Add List operation in Anypoint Connector for NetSuite (NetSuite Connector) limited concurrent connections in the Batch Aggregator component.</p></div></div></td></tr><tr><td><div><div><p>SE-19515/MULE-19209</p></div></div></td><td><div><div><p>Fixed an issue that caused a memory leak when using a <code>try</code> block.</p></div></div></td></tr><tr><td><div><div><p>SE-19294</p></div></div></td><td><div><div><p>Resolved an issue in which the application received a <code>rejected from Scheduler</code> exception for HTTP request configurations when processing concurrent requests.</p></div></div></td></tr><tr><td><div><div><p>SE-19327</p></div></div></td><td><div><div><p>Fixed a <code>SerializationException</code> error that occurred when using the quote reader property (<code>quote="\""</code>) with a batch component.</p></div></div></td></tr><tr><td><div><div><p>SE-19557/MULE-19218</p></div></div></td><td><div><div><p>Resolved an issue that prevented opening a new cursor on a closed stream.</p></div></div></td></tr><tr><td><div><div><p>SE-19606</p></div></div></td><td><div><div><p>Fixed a problem in which database connections weren’t returned to the pool or were returned with a delay.</p></div></div></td></tr><tr><td><div><div><p>SE-19080/MULE-19157</p></div></div></td><td><div><div><p>Fixed an issue in which a connector with an operation that has a parameter group with exclusive optionals (one required) and one of the optional parameters is a POJO with dynamic fields caused the application deployment to fail. Affected connectors are the Cryptography module and Anypoint Connector for SAP (SAP Connector).</p></div></div></td></tr></tbody></table>

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

## February 2021

Patch release version: 4.3.0-20210119

The February patch update adddresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>MULE-19076</p></div></div></td><td><div><div><p>Added warning when the remove variable component tries to remove a non existing variable.</p></div></div></td></tr><tr><td><div><div><p>MULE-19038/SE-17832</p></div></div></td><td><div><div><p>Fixed a property <code>{app.name}</code> conflict when the application is deployed to CloudHub.</p></div></div></td></tr><tr><td><div><div><p>SE-18778</p></div></div></td><td><div><div><p>MUnit is unable to dynamic lookup flow references.</p></div></div></td></tr><tr><td><div><div><p>MULE-19122/SE-19029</p></div></div></td><td><div><div><p>Fixed an issue where different instances of a dynamic configuration containing an OAuth setup with Client Credentials could share the same token causing various errors (such as login fail or unauthorised access).</p></div></div></td></tr><tr><td><div><div><p>MULE-19129/SE-19069</p></div></div></td><td><div><div><p>Resolved a problem in which the CloudHub scheduler got stuck intermittently.</p></div></div></td></tr><tr><td><div><div><p>MULE-19118/SE-18583</p></div></div></td><td><div><div><p>Fixed an issue affecting the error handling of applications making use of the Try scope in subflows. This affected error propagation from subflows to their parent related flows.</p></div></div></td></tr><tr><td><div><div><p>MULE-18873</p></div></div></td><td><div><div><p>Resolved an issue in which routes dropped events during Flow Reference processing in applications that combined Scatter-Gather and Flow Reference components.</p></div></div></td></tr><tr><td><div><div><p>MULE-19113/SE-19102</p></div></div></td><td><div><div><p>Added logger to BackPressureStrategySelector for better debugging and tracing.</p></div></div></td></tr><tr><td><div><div><p>SE-18335</p></div></div></td><td><div><div><p>Fixed NullPointerException when using the HTTP Connector inside of a Connector built with XML SDK.</p></div></div></td></tr><tr><td><div><div><p>MULE-19097/SE-19126</p></div></div></td><td><div><div><p>Fixed issue that cuased CorrelationID to no be consistent throught the Event execution due to unwanted change in the used ClassLoader.</p></div></div></td></tr><tr><td><div><div><p>MULE-18159/SE-15096</p></div></div></td><td><div><div><p>Fixed an issue where plugins declared in domain could not load classes at application level.</p></div></div></td></tr><tr><td><div><div><p>MULE-19088/SE-18749</p></div></div></td><td><div><div><p>Fixed an issue that caused a <code>Java.lang.NullPointerException</code> error when trying to run MUnit tests on 4.3.0.</p></div></div></td></tr><tr><td><div><div><p>SE-17625</p></div></div></td><td><div><div><p>Fixed problem where the error handler component was called multiple times by Until Successful scope incorrectly.</p></div></div></td></tr><tr><td><div><div><p>MULE-19068/SE-18382</p></div></div></td><td><div><div><p>Fixed an issue that caused intermittent <code>Cannot open a new cursor on a closed stream</code> errors.</p></div></div></td></tr><tr><td><div><div><p>MULE-19049/SE-18521</p></div></div></td><td><div><div><p>Resolved incorrect behavior of the First Successful scope that occurred when the scope was within an Error Handler component.</p></div></div></td></tr><tr><td><div><div><p>MULE-18679</p></div></div></td><td><div><div><p>Fixed a ConcurrentModificationError on adding an startup listener while deploying an app.</p></div></div></td></tr><tr><td><div><div><p>EE-7624</p></div></div></td><td><div><div><p>Upgrade Tanuki wrapper to 3.5.45.</p></div></div></td></tr><tr><td><div><div><p>SE-18407</p></div></div></td><td><div><div><p>Fixed unexpected error <code>The mapper returned a null value.</code> within a Cache scope.</p></div></div></td></tr><tr><td><div><div><p>EE-7610/SE-18524</p></div></div></td><td><div><div><p>Fixed an issue that caused failures to deserialize file store based stream payload in batch.</p></div></div></td></tr><tr><td><div><div><p>AGW-4533</p></div></div></td><td><div><div><p>Fixed API reporting for requests with 0 size incoming requests (like GET requests).</p></div></div></td></tr><tr><td><div><div><p>DW-325</p></div></div></td><td><div><div><p>DataWeave: NDJson was not working when being executed in parallel.</p></div></div></td></tr><tr><td><div><div><p>MULE-19140/DW-371</p></div></div></td><td><div><div><p>DataWeave: Fixed an issue with property handling.</p></div></div></td></tr><tr><td><div><div><p>SE-13423</p></div></div></td><td><div><div><p>DataWeave: Fixed an issue where FlatFile cannot write <code>dw</code> keys as values.</p></div></div></td></tr><tr><td><div><div><p>SE-14799</p></div></div></td><td><div><div><p>Fixed problem where the <code>onErrorContinue</code> cannot catch a mapped error thrown from a sub flow.</p></div></div></td></tr><tr><td><div><div><p>SE-17677</p></div></div></td><td><div><div><p>DataWeave: Added feature where the <code>BinaryValue</code> read buffer is now configurable with the property <code>com.mulesoft.dw.buffersize</code>.</p></div></div></td></tr><tr><td><div><div><p>SE-18882</p></div></div></td><td><div><div><p>DataWeave: Fixed the behavior of the <code>substringBefore()</code> and <code>substringBeforeLast()</code> functions which produced incorrect outputs.</p></div></div></td></tr><tr><td><div><div><p>SE-19000</p></div></div></td><td><div><div><p>DataWeave: Added a new reader property called <code>tableLimit</code> to control the boundaries of where to read data. Options are: <code>HeaderSize</code>, <code>Unbounded</code>, or the name of the column.</p></div></div></td></tr><tr><td><div><div><p>SE-19086</p></div></div></td><td><div><div><p>DataWeave: Fixed an issue where stream batching did not work in deferred mode.</p></div></div></td></tr><tr><td><div><div><p>SE-19094</p></div></div></td><td><div><div><p>DataWeave: Fixed an issue where using <code>for each</code> with batchsize caused the stream to close (<code>StreamClose</code>).</p></div></div></td></tr><tr><td><div><div><p>SE-19040</p></div></div></td><td><div><div><p>DataWeave: Fixed an issue that caused a <code>NullPointerException</code> when the message of the exception was <code>null</code>.</p></div></div></td></tr><tr><td><div><div><p>SE-16997/MULE-18675</p></div></div></td><td><div><div><p>Fixed an issue in which using dynamic configurations for paged or streaming operations caused a disconnection error when trying to consume the pages or the stream.</p></div></div></td></tr></tbody></table>

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

## January 2021

Patch release version: 4.3.0-20210105

The January patch update adddresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>MULE-19014</p></div></div></td><td><div><div><p>Upgraded Bouncy Castle to version 1.67.</p></div></div></td></tr><tr><td><div><div><p>MULE-19026</p></div></div></td><td><div><div><p>Fixed incorrect reconnection behavior in sources, such as the Anypoint Connector for SFTP (SFTP Connector), which caused the sources to work incorrectly.</p></div></div></td></tr><tr><td><div><div><p>MULE-18599</p></div></div></td><td><div><div><p>Fixed an issue that produced an incorrect value for the partial fetching key resolution when a Parameter Group that is the MetadataKey used the setting <code>showInDsl=true</code>.</p></div></div></td></tr><tr><td><div><div><p>MULE-19016</p></div></div></td><td><div><div><p>Fixed an issue that could cause a <code>"NullPointerError"</code> when using the Post Message operation of Anypoint Connector for Slack (Slack Connector).</p></div></div></td></tr><tr><td><div><div><p>MULE-19006, SE-18378</p></div></div></td><td><div><div><p>Fixed an issue that produced a <code>can’t get statistics before initialise() is invoked</code> error when using a dynamic expiration configuration in a clustered environment.</p></div></div></td></tr><tr><td><div><div><p>MULE-19002, SE-17479</p></div></div></td><td><div><div><p>Fixed an issue in the XML SDK that ignored complex parameters defined as string arrays and with the <code>behavior</code> role.</p></div></div></td></tr><tr><td><div><div><p>MULE-18537</p></div></div></td><td><div><div><p>Mule now logs reconnection attempts when using the Standard Reconnection Strategy for any connector.</p></div></div></td></tr><tr><td><div><div><p>MULE-18929, SE-18107</p></div></div></td><td><div><div><p>Fixed an issue in which <code>ActivePolicies</code> set in <code>DefaultPolicyManager</code> retained multiple (weak) references to policies when expired policies renewed. The references were not collected. To avoid consuming more memory than necessary, the fix ensures that only one weak reference is retained per policy.</p></div></div></td></tr><tr><td><div><div><p>EE-7443, SE-16276</p></div></div></td><td><div><div><p>Fixed an issue in running Batch jobs that caused the jobs to get stuck and never finish.</p></div></div></td></tr><tr><td><div><div><p>SE-16965, AGW-4497</p></div></div></td><td><div><div><p>Fixed a metaspace classloader leak that occurred during the redeployment of an application.</p></div></div></td></tr><tr><td><div><div><p>SE-16372</p></div></div></td><td><div><div><p>Fixed an issue that prevented DataWeave from properly retrieving values when reading CSV files with Byte Order Mark (BOM) and Streaming enabled (<code>streaming=true</code>).</p></div></div></td></tr><tr><td><div><div><p>SE-18393</p></div></div></td><td><div><div><p>Fixed a DataWeave issue that resulted in a <code>null</code> value when using variables (vars) that were not resolved correctly.</p></div></div></td></tr><tr><td><div><div><p>SE-18136</p></div></div></td><td><div><div><p>Fixed a DataWeave issue that occurred when reading Excel files with empty columns, which caused rows to shift incorrectly to that empty space to fill in the empty column.</p></div></div></td></tr><tr><td><div><div><p>SE-18580</p></div></div></td><td><div><div><p>Fixed an issue that caused the Set Variable operation to fail with a <code>MULE:EXPRESSION</code> error when using a DataWeave expression that contained a function definition.</p></div></div></td></tr><tr><td><div><div><p>DW-289</p></div></div></td><td><div><div><p>Fixed an issue in which upserting an object with <code>update</code> duplicated key-value pairs in some cases.</p></div></div></td></tr><tr><td><div><div><p>DW-306</p></div></div></td><td><div><div><p>Fixed an issue that prevented the <code>update</code> operator from selecting attributes.</p></div></div></td></tr><tr><td><div><div><p>DW-307</p></div></div></td><td><div><div><p>Fixed an issue that prevented processing of XML documents when streaming mode was enabled.</p></div></div></td></tr><tr><td><div><div><p>MULE-18990</p></div></div></td><td><div><div><p>Added an optional warning with information about when an event is dropped.</p></div></div></td></tr><tr><td><div><div><p>MULE-19015</p></div></div></td><td><div><div><p>Fixed a <code>Cannot open a new cursor on a closed stream</code> error that occurred when using a nested <code>foreach</code> with a batch size larger than 1.</p></div></div></td></tr><tr><td><div><div><p>MULE-18949</p></div></div></td><td><div><div><p>Fixed a regression caused by a prior fix (MULE-18805) that made DataSense scenarios with error handling work improperly. With this fix, every scenario works properly, including the ones from MULE-18805.</p></div></div></td></tr><tr><td><div><div><p>SE-14750, MULE-19019</p></div></div></td><td><div><div><p>Fixed an issue that added a <code>'Content-length: 0'</code> header for HTTP methods with undefined body semantics (GET, HEAD, and DELETE).</p></div></div></td></tr><tr><td><div><div><p>EE-7582</p></div></div></td><td><div><div><p>Fixed an HTTP service regression in which an unexpected error was thrown on a <code>SoapFault</code>.</p></div></div></td></tr></tbody></table>

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

## November 2020

Patch release version: 4.3.0-20201021

The November patch update adddresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>Description</th></tr></thead><tbody><tr><td><div></div></td><td><div><div><p>Improved application network metric tracking.</p></div></div></td></tr><tr><td><div><div><p>SE-17806/MULE-18883</p></div></div></td><td><div><div><p>Fixed a CloudHub issue in which the Scheduler stopped but reported its status as <code>Running</code>.</p></div></div></td></tr><tr><td><div><div><p>SE-17445/MULE-18885</p></div></div></td><td><div><div><p>Fixed an issue in which the queue manager leaked queue configuration instances when using Anypoint Connector for Virtual Machine (VM Connector) in cluster deployment setups.</p></div></div></td></tr><tr><td><div><div><p>SE-16989/MULE-18805</p></div></div></td><td><div><div><p>Fixed an issue in which MUnit did not successfully execute due to improper functioning (caused by lazy loading logic) when using an On-Error component.</p></div></div></td></tr><tr><td><div><div><p>SE-17092/MULE-18777</p></div></div></td><td><div><div><p>Resolved a problem with Anypoint Connector for AMQP (AMQP Connector) that caused the channel count to increase incorrectly after force-closing connections.</p></div></div></td></tr><tr><td><div><div><p>SE-16853/MULE-18889</p></div></div></td><td><div><div><p>Resolved an execution problem that occurred when an application used Groovy with Scripting module version 2.0.0.</p></div></div></td></tr><tr><td><div><div><p>MULE-18884</p></div></div></td><td><div><div><p>Resolved a memory leak that caused Mule runtime engine to crash after multiple redeployments of an app.</p></div></div></td></tr><tr><td><div><div><p>SE-15000/MULE-18794</p></div></div></td><td><div><div><p>Fixed an issue in which DataSense was unable to find the WSDL file for APIkit for SOAP Project.</p></div></div></td></tr><tr><td><div><div><p>SE-16933/MULE-18698</p></div></div></td><td><div><div><p>Fixed a regression in which dynamic configurations were not properly disposed, which caused out of memory errors.</p></div></div></td></tr><tr><td><div><div><p>SE-17756/MULE-18803</p></div></div></td><td><div><div><p>Fixed an error that could cause a flow to stop when combining the Scatter-Gather component or Parallel For Each scope with the Choice or Round Robin routers.</p></div></div></td></tr><tr><td><div><div><p>SE-16596/DW-240</p></div></div></td><td><div><div><p>Fixed an issue in the DataWeave flat file component in which some <code>null</code> values were not transformed to zeroes in hexadecimal.</p></div></div></td></tr><tr><td><div><div><p>SE-17773</p></div></div></td><td><div><div><p>Added a new system property <code>com.mulesoft.dw.valueSelector.selectsAlwaysFirst</code> to avoid caching selected indexes in DataWeave.</p></div></div></td></tr><tr><td><div><div><p>SE-17873</p></div></div></td><td><div><div><p>Fixed the following DataWeave error that occurred while converting <code>Instant</code> to <code>LocalDateTime</code> with <code>MIN</code> and <code>MAX</code>:</p></div><div><p><code>An exception occurred while trying to access field function java.time.Instant.MIN. Caused by: java.time.DateTimeException: Invalid value for Year</code></p></div></div></td></tr><tr><td><div><div><p>FV-833</p></div></div></td><td><div><div><p>Fixed an issue in which <code>joinBy</code> failed to validate against signatures in DataWeave. //correct issue number?</p></div></div></td></tr><tr><td><div><div><p>SE-9907</p></div></div></td><td><div><div><p>Fixed an issue with DataWeave in which <code>java.util.Timezone</code> provided a <code>ZoneInfo</code> Java class, rather than the time zone ID, such as "America/Los Angeles".</p></div></div></td></tr><tr><td><div><div><p>SE-14220</p></div></div></td><td><div><div><p>Fixed a <code>NullPointerException</code> error that occurred when using the Flat File format in DataWeave.</p></div></div></td></tr><tr><td><div><div><p>SE-15970</p></div></div></td><td><div><div><p>Resolved an issue with the DataWeave <code>diff</code> function, which inverted the values of the <code>expected</code> and <code>actual</code> keys.</p></div></div></td></tr><tr><td><div><div><p>SE-16350</p></div></div></td><td><div><div><p>Fixed a DataWeave issue in which using <code>header=false</code> with <code>bodyStartLineNumber</code>, the CSV reader skipped lines.</p></div></div></td></tr><tr><td><div><div><p>SE-16883</p></div></div></td><td><div><div><p>Fixed an issue with the DataWeave <code>Mule::causedBy</code> function, which didn’t have the correct type defined for <code>Error</code>.</p></div></div></td></tr><tr><td><div><div><p>SE-17149</p></div></div></td><td><div><div><p>Resolved an issue in DataWeave conversion from Excel to CSV format, which did not print cells when the cell value was empty, resulting in an inconsistent output.</p></div></div></td></tr><tr><td><div><div><p>SE-17212</p></div></div></td><td><div><div><p>Resolved a problem in which defining a Client ID Enforcement policy failed with encrypted client credentials.</p></div></div></td></tr><tr><td><div><div><p>SE-17392</p></div></div></td><td><div><div><p>Fixed an issue in which DataWeave didn’t correctly handle an internal <code>UnsupportedTypeCoercionException</code> error while processing a batch of records.</p></div></div></td></tr><tr><td><div><div><p>SE-17446</p></div></div></td><td><div><div><p>Resolved an issue in DataWeave in which conversion from Excel to DataWeave didn’t correctly ignore empty lines in Excel.</p></div></div></td></tr><tr><td><div><div><p>SE-17520</p></div></div></td><td><div><div><p>Fixed a problem in which DataWeave didn’t correctly process keys that use a literal <code>$</code> string value.</p></div></div></td></tr><tr><td><div><div><p>SE-17562</p></div></div></td><td><div><div><p>Fixed a problem in which a migrated MUnit test from a previous Mule version executed a mocked connector.</p></div></div></td></tr><tr><td><div><div><p>SE-17570</p></div></div></td><td><div><div><p>Resolved a DataWeave issue that caused a <code>StackOverflow</code> error when using <code>some</code> and <code>every</code> functions with large arrays.</p></div></div></td></tr><tr><td><div><div><p>SE-13715/MULE-18812</p></div></div></td><td><div><div><p>Fixed an issue that occurred after Mule runtime engine restarted, which caused Mule application deployment failures while parsing domain shared resources.</p></div></div></td></tr><tr><td><div><div><p>SE-12712/MULE-17880</p></div></div></td><td><div><div><p>Fixed multiple WARN log entries that occurred when using a caching strategy.</p></div></div></td></tr><tr><td><div><div><p>SE-15592/MULE-18573</p></div></div></td><td><div><div><p>Fixed an issue that occurred when an app transformed data using variables.</p></div></div></td></tr><tr><td><div><div><p>MULE-18872</p></div></div></td><td><div><div><p>Fixed an issue with the runtime logging that could cause out of memory issues.</p></div></div></td></tr><tr><td><div><div><p>SE-16439/MULE-18696</p></div></div></td><td><div><div><p>Resolved a problem that occurred when processing a large batch of records within a Parallel For Each scope, causing an exception and an unresponsive application.</p></div></div></td></tr><tr><td><div><div><p>SE-16823/MULE-18712</p></div></div></td><td><div><div><p>Resolved a problem in which it was not possible to mock <code>scripting:execute</code> processors when running MUnit tests.</p></div></div></td></tr><tr><td><div><div><p>SE-17554/MULE-18739</p></div></div></td><td><div><div><p>Fixed the default value resolution for the Scheduler component’s <code>disallowConcurrentExecution</code> attribute so that you don’t need to define it explicitly.</p></div></div></td></tr><tr><td><div><div><p>MULE-18742</p></div></div></td><td><div><div><p>Fixed a race condition that produced a <code>ConcurrentModificationException</code> error in <code>Log4jContextFactory</code> when canceling a registered callback while disposing an application.</p></div></div></td></tr></tbody></table>

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

## September 2020

Patch release version: 4.3.0-20200824

The September patch update adddresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>MULE-18694/SE-16719</p></div></div></td><td><div><div><p>Resolved an issue that caused applications to fail due to memory consumption when referencing nested subflows (using <code>&lt;flow-ref&gt;</code>).</p></div></div></td></tr><tr><td><div><div><p>MULE-18666</p></div></div></td><td><div><div><p>Fixed an issue that caused a <code>StackOverflowException</code> error when using the following DataWeave script:</p></div><div><div><pre>#[output application/json --- message]</pre></div></div></div></td></tr><tr><td><div><div><p>MULE-18689/SE-16734</p></div></div></td><td><div><div><p>Corrected a memory leak referencing the following class in the runtime logs:</p></div><div><div><pre><code data-lang="xml">org.mule.runtime.core.privileged.exception.
TemplateOnErrorHandler$
OnErrorHandlerFluxObjectFactorytransactional</code></pre></div></div></div></td></tr><tr><td><div><div><p>MULE-18682</p></div></div></td><td><div><div><p>Fixed a problem that caused a <code>ClassNotFoundException</code> after a policy upgrade affecting proxy applications.</p></div></div></td></tr><tr><td><div><div><p>MULE-18657/SE-14959</p></div></div></td><td><div><div><p>Fixed a problem that prevented primary node initialization in Anypoint Connector for Salesforce (Salesforce Connector).</p></div></div></td></tr><tr><td><div><div><p>MULE-18665/SE-16278</p></div></div></td><td><div><div><p>Fixed the <code>RegistryLifecycleCallback</code> logger so that it no longer prints the customer’s security key.</p></div></div></td></tr><tr><td><div><div><p>MULE-18542/SE-15818</p></div></div></td><td><div><div><p>Resolved a thread leak when redeploying an application that uses Anypoint Connector for Database (Database Connector) and references the Oracle JDBC driver.</p></div></div></td></tr><tr><td><div><div><p>MULE-18628/SE-16435</p></div></div></td><td><div><div><p>Resolved a problem in which applications were unable to retrieve objects from the cache due to serialization issues.</p></div></div></td></tr><tr><td><div><div><p>MULE-18623/SE-16933</p></div></div></td><td><div><div><p>Corrected a memory leak that occurred when using dynamic configurations.</p></div></div></td></tr><tr><td><div><div><p>SE-15453</p></div></div></td><td><div><div><p>DataWeave’s XML module now includes a new property to handle escaping <code>&gt;</code> characters.</p></div></div></td></tr><tr><td><div><div><p>SE-15249</p></div></div></td><td><div><div><p>Fixed DataWeave attribute selector not dispatching to the correct implementation.</p></div></div></td></tr><tr><td><div><div><p>SE-15362</p></div></div></td><td><div><div><p>Fixed <code>NullPointerException</code> in DataWeave’s XML module.</p></div></div></td></tr><tr><td><div><div><p>DW-184/SE-15834</p></div></div></td><td><div><div><p>Fixed DataWeave inferred types when the output is undefined storage to recalculate output.</p></div></div></td></tr><tr><td><div><div><p>SE-15894</p></div></div></td><td><div><div><p>JSON binary values are now encoded into strings consistently across DataWeave versions.</p></div></div></td></tr><tr><td><div><div><p>SE-16462</p></div></div></td><td><div><div><p>DataWeave now parses single key-value pairs correctly when mixed with conditionals.</p></div></div></td></tr><tr><td><div><div><p>SE-16539</p></div></div></td><td><div><div><p>Fixed an error that occurred in DataWeave when parsing JSON with whitespace between array elements.</p></div></div></td></tr><tr><td><div><div><p>SE-16167</p></div></div></td><td><div><div><p>The DataWeave Avro module now correctly converts logical types.</p></div></div></td></tr><tr><td><div><div><p>AGW-4287/SE-16981</p></div></div></td><td><div><div><p>Fixed an issue that caused object-store deserialization errors when upgrading the internal version of Rate Limiting policy.</p></div></div></td></tr><tr><td><div><div><p>SE-17193</p></div></div></td><td><div><div><p>Fix a deployment issue that occurred for apps with multiple nested function calls, such as <code>++</code>, in DataWeave.</p></div></div></td></tr><tr><td><div><div><p>SE-17270</p></div></div></td><td><div><div><p>Fixed an issue in which the primary node in a cluster remained primary after stopping the runtime, causing applications with a pooling processor on the primary node to stop working.</p></div></div></td></tr><tr><td><div><div><p>MULE-18604/SE-12900</p></div></div></td><td><div><div><p>Fixed an issue in which NTLM authentication-dancing failed when performing multiple parallel requests requiring renegotiation.</p></div></div></td></tr></tbody></table>

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

## August 2020

Patch release version: 4.3.0-20200727

The August patch update adddresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>MULE-18535, SE-16524</p></div></div></td><td><div><div><p>Fixed incorrect behavior in which accessing <code>message.message.exceptionPayload.info.Element</code> returned <code>null</code> instead of an error.</p></div></div></td></tr><tr><td><div><div><p>MULE-18528</p></div></div></td><td><div><div><p>SDK OAuth authorization code-flow references do not have a stereotype making it fail when executed from MUnit.</p></div></div></td></tr><tr><td><div><div><p>MULE-18579</p></div></div></td><td><div><div><p>Resolved an issue in which when an object store expired, it loaded all deserialized entries into memory, doubling memory consumption.</p></div></div></td></tr><tr><td><div><div><p>MULE-18564</p></div></div></td><td><div><div><p>Fixed an issue in which using inline proxy configuration in the OAuth module failed to create the <code>requestConfig</code> configuration.</p></div></div></td></tr><tr><td><div><div><p>MULE-18569, SE-16282</p></div></div></td><td><div><div><p>Resolved an issue in which the Anypoint Connector for Kafka returned the <code>java.nio.file.InvalidPathException: Illegal char &lt;:&gt;</code> exception when accessing filesystem configuration files.</p></div></div></td></tr><tr><td><div><div><p>MULE-18548, SE-14272</p></div></div></td><td><div><div><p>Fixed an issue in which the Cache scope in a cluster configuration did not effectively monitor the cache in the secondary node.</p></div></div></td></tr><tr><td><div><div><p>MULE-18545</p></div></div></td><td><div><div><p>Resolved an <code>IndexOutOfBoundsException</code> error that occurred when handling a backpressure error in a source policy.</p></div></div></td></tr><tr><td><div><div><p>MULE-16688</p></div></div></td><td><div><div><p>Fixed a problem that occurred when using a property placeholder on an <code>import</code> tag with <code>deploymentProperties</code> that caused the placeholders to not be replaced.</p></div></div></td></tr><tr><td><div><div><p>MULE-18513</p></div></div></td><td><div><div><p>Fixed an issue in which a connector configuration using OAuth caused metadata-resolution problems.</p></div></div></td></tr><tr><td><div><div><p>MULE-18504</p></div></div></td><td><div><div><p>Resolved an SDK regression in which the component reference in an operation chain was wrongly calculated.</p></div></div></td></tr><tr><td><div><div><p>EE-7381</p></div></div></td><td><div><div><p>Fixed an issue in which creating a <code>scheduledThreadPool</code> with a <code>coreSize</code> value of 0 could cause high CPU utilization.</p></div></div></td></tr><tr><td><div><div><p>SE-16468</p></div></div></td><td><div><div><p>Fixed an issue in which DataWeave <code>skipNullOn</code> did not behave properly because the value <code>null</code> was ignored in maps.</p></div></div></td></tr><tr><td><div><div><p>SE-16915</p></div></div></td><td><div><div><p>Removed unnecessary log messages that appeared when using dynamic objects in DataWeave.</p></div></div></td></tr><tr><td><div><div><p>MULE-18196, SE-16894</p></div></div></td><td><div><div><p>The fix for the SE-15056 issue causes applications that use custom policies to fail when sharing the <code>ErrorType</code> repository if the app and policy bundle didn’t include all dependencies.</p></div><div><p>+ You can revert the behavior by setting the <code>mule.share.errorTypeRepository</code> system property to <code>true</code>.</p></div></div></td></tr><tr><td><div><div><p>SE-13603</p></div></div></td><td><div><div><p>Fixed an issue in which an application using more than one <code>salesforce:replay-channel</code> operation failed with status code 429.</p></div></div></td></tr><tr><td><div><div><p>SE-13603, SE-10677, SE-16728</p></div></div></td><td><div><div><p>Upgraded the Object Store v2 plugin to version 4.0.27.</p></div></div></td></tr></tbody></table>

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

## July 2020

Patch release version: 4.3.0-20200622

The July patch update adddresses the following issues:

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>AGW-4211, SE-16370</p></div></div></td><td><div><div><p>Fixed an issue in which applications using APIkit and policies with the autodiscovery component incorrectly returned 500 instead of 404.</p></div></div></td></tr><tr><td><div><div><p>MULE-18454</p></div></div></td><td><div><div><p>Resolved a problem generating XML when creating an artifact declaration that contains a platform-managed OAuth connection provider.</p></div></div></td></tr><tr><td><div><div><p>MULE-18475, SE-16232</p></div></div></td><td><div><div><p>Fixed a <code>NullPointerException</code> issue on the XML SDK framework when a parameter that has both <code>CONTENT</code> and <code>OPTIONAL</code> values is empty.</p></div></div></td></tr><tr><td><div><div><p>MULE-18491, SE-16370</p></div></div></td><td><div><div><p>Errors without <code>location</code> values no longer cause policy error handling to behave like a back-pressure error.</p></div></div></td></tr><tr><td><div><div><p>MULE-18506, SE-16470</p></div></div></td><td><div><div><p>Reverted MULE-18370 because it caused a key collision in the <code>ManagedCursorProvider</code> cache management.</p></div></div></td></tr><tr><td><div><div><p>SE-13383</p></div></div></td><td><div><div><p>Fixed an issue that occurred while moving corrupted domain object store files to the <code>Garbage</code> folder.</p></div></div></td></tr><tr><td><div><div><p>SE-15067</p></div></div></td><td><div><div><p>DataWeave now properly handles the <code>#[</code> sequence inside a String value in Mule operations, such as Logger.</p></div></div></td></tr><tr><td><div><div><p>MULE-18375, SE-15704</p></div></div></td><td><div><div><p>Fixed a problem in which a custom policy that applied an outbound request changed the behavior of an API by clearing attributes.</p></div></div></td></tr><tr><td><div><div><p>SE-15918</p></div></div></td><td><div><div><p>Added support for escaped Char sequences on DataWeave settings.</p></div></div></td></tr><tr><td><div><div><p>MULE-18458, SE-15925</p></div></div></td><td><div><div><p>Fixed a problem that occurred when resolving DataWeave errors and processing the flow stack.</p></div></div></td></tr><tr><td><div><div><p>MULE-18439, SE-15995</p></div></div></td><td><div><div><p>Fixed an application deployment failure with the <code>loops not allowed</code> error.</p></div></div></td></tr><tr><td><div><div><p>SE-16006</p></div></div></td><td><div><div><p>Fixed an issue that prevented debugging an application in Studio 7.5 and Mule runtime engine 4.3.</p></div></div></td></tr><tr><td><div><div><p>MULE-18462, SE-16038</p></div></div></td><td><div><div><p>Resolved an issue in which combining Cache and For Each scopes caused a <code>java.lang.ArrayIndexOutOfBoundsException: 0</code> error during execution.</p></div></div></td></tr><tr><td><div><div><p>MULE-18501, MULE-18500, SE-16088</p></div></div></td><td><div><div><p>Fixed a regression with MUnit spy assertions (<code>before-call</code> and <code>after-call</code>) that was introduced in Mule 4.3.0.</p></div></div></td></tr><tr><td><div><div><p>MULE-18498, MULE-18480, SE-16095</p></div></div></td><td><div><div><p>Fixed an <code>OutOfMemoryError: Metaspace</code> error on applications with multiple concurrent deployments and some redeployments.</p></div></div></td></tr><tr><td><div><div><p>MULE-18453, SE-16119</p></div></div></td><td><div><div><p>Fixed an issue with backslash-character processing when running Studio on Windows, which caused <strong>Test Connection</strong> in Anypoint Connector for File to fail when the <code>Configuration</code> property was present.</p></div></div></td></tr><tr><td><div><div><p>MULE-18488, SE-16133</p></div></div></td><td><div><div><p>Fixed a <code>NullPointerException</code> error that occurred when using Anypoint Connector for Database in a Try scope and running it more than once.</p></div></div></td></tr><tr><td><div><div><p>MULE-18489, SE-16281</p></div></div></td><td><div><div><p>Resolved the <code>ClassCastException: java.lang.Integer cannot be cast to java.lang.Long</code> error when using Anypoint Connector for Kafka.</p></div></div></td></tr><tr><td><div><div><p>SE-16292</p></div></div></td><td><div><div><p>Fixed a JSON payload with spaces after an array value failed in DataWeave’s in-memory parser.</p></div></div></td></tr><tr><td><div><div><p>MULE-18490, SE-16317</p></div></div></td><td><div><div><p>Resolved a problem accessing <code>flow.name</code> in DataWeave transformations.</p></div></div></td></tr><tr><td><div><div><p>MULE-18492, SE-16365</p></div></div></td><td><div><div><p>Fixed a serialization problem with policies using the 'Rate limit SLA' policy.</p></div></div></td></tr><tr><td><div><div><p>SE-16379</p></div></div></td><td><div><div><p>Fixed an application start-up error <code>NoSuchBeanDefinitionException: No qualifying bean of type 'org.mule.extensions.java.internal.cache.JavaModuleLoadingCache' available</code>.</p></div></div></td></tr><tr><td><div><div><p>SE-16381</p></div></div></td><td><div><div><p>Resolved a problem processing DataWeave date expressions when calculating year differences.</p></div></div></td></tr><tr><td><div><div><p>SE-16389</p></div></div></td><td><div><div><p>Fixed an issue in which DataWeave nested dynamic objects skipped elements.</p></div></div></td></tr><tr><td><div><div><p>SE-16431</p></div></div></td><td><div><div><p>Cached DataWeave compiled expressions based on string script to avoid an out-of-memory issue on deployment.</p></div></div></td></tr><tr><td><div><div><p>MDM-106, SE-16066</p></div></div></td><td><div><div><p>Fixed metadata that was not generated correctly when a <code>&lt;ROW&gt;</code> tag was duplicated.</p></div></div></td></tr><tr><td><div><div><p>MULE-18431</p></div></div></td><td><div><div><p>Corrected problems in which threads hung when using Anypoint Connector for Virtual Machine under load.</p></div></div></td></tr><tr><td><div><div><p>MULE-18294</p></div></div></td><td><div><div><p>Resolved an issue in which polling source Scheduler components incorrectly restarted on reconnection.</p></div></div></td></tr><tr><td><div><div><p>MULE-18440</p></div></div></td><td><div><div><p>Fixed a race condition that occurred when a thread looked for policies and invalidated the cache simultaneously.</p></div></div></td></tr><tr><td><div><div><p>MULE-18442</p></div></div></td><td><div><div><p>Mule no longer creates a default policy manager for each applied policy.</p></div></div></td></tr></tbody></table>

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

## June 2020

Patch release version: 4.3.0-20200521

This patch release consolidates fixes to Mule 4.3.0 since the initial release on April 30, 2020. The
fixes extend through June 2020.

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>AGW-4199</p></div></div></td><td><div><div><p>Fixed an error that occurred when accessing Gatekeeper and Analytics policy templates.</p></div></div></td></tr><tr><td><div><div><p>SE-15935</p></div></div></td><td><div><div><p>Mule application threw the wrong HTTP response status code when <code>api-gateway:autodiscovery</code> was enabled.</p></div></div></td></tr><tr><td><div><div><p>MULE-18421</p></div></div></td><td><div><div><p>When using a logger to log a value, a result containing <code>##[</code> is no longer incorrectly reevaluated.</p></div></div></td></tr><tr><td><div><div><p>MULE-18416</p></div></div></td><td><div><div><p>Resolved <code>ClassCastException</code> when running an API using the Interception API.</p></div></div></td></tr><tr><td><div><div><p>MULE-18397</p></div></div></td><td><div><div><p>Fixed an error that occurred when an expression accessed a target-operation payload attribute.</p></div></div></td></tr><tr><td><div><div><p>MULE-18390</p></div></div></td><td><div><div><p>Fixed an <code>OutOfMemory</code> error that mentioned running out of Metaspace when running MUnit tests.</p></div></div></td></tr><tr><td><div><div><p>MULE-18378</p></div></div></td><td><div><div><p>When an HTTP Listener is source of the flow, trying to reference a flow variable from the flow’s error response builder, the variable could not be found if a source policy was applied to the Listener.</p></div></div></td></tr><tr><td><div><div><p>MULE-18371</p></div></div></td><td><div><div><p>Fixed a <code>NullPointerException</code> error that occurred when processing a request and all in-flight cursors were inappropriately closed.</p></div></div></td></tr><tr><td><div><div><p>MULE-18370</p></div></div></td><td><div><div><p>Fixed an issue that might rarely cause a key collision with the <code>ManagedCursorProvider</code> cache.</p></div></div></td></tr><tr><td><div><div><p>MULE-18369</p></div></div></td><td><div><div><p><code>MULE:OVERLOAD</code> exception is thrown when first policy contains a Cache scope and second policy contains a Try scope error-handler.</p></div></div></td></tr><tr><td><div><div><p>MULE-18364</p></div></div></td><td><div><div><p>Fixed a problem that prevented an application from starting after stopping using Runtime Manager.</p></div></div></td></tr><tr><td><div><div><p>MULE-18312</p></div></div></td><td><div><div><p>A custom global error handler is no longer ignored when located after a failing flow.</p></div></div></td></tr><tr><td><div><div><p>MULE-18306</p></div></div></td><td><div><div><p>Fixed a race condition that occurred while disposing flows using a <code>until-successful</code> construct.</p></div></div></td></tr><tr><td><div><div><p>MULE-18284</p></div></div></td><td><div><div><p>Fixed an issue where a policy deployment failed under certain circumstances because the <code>errorType</code> could not be found when deploying a policy.</p></div></div></td></tr><tr><td><div><div><p>MULE-18264</p></div></div></td><td><div><div><p>Resolved open JAR file-leak when reading resources, such as keystore, when configuring TLS.</p></div></div></td></tr><tr><td><div><div><p>MULE-18255</p></div></div></td><td><div><div><p>OCSClient now supports configuring the API version of the service via system property.</p></div></div></td></tr><tr><td><div><div><p>MULE-18244</p></div></div></td><td><div><div><p>Fixed a classloading issue when connectors that use third-party libraries are not able to load classes if they rely on loadClass(s,b) from <code>CompositeClassLoader</code>.</p></div></div></td></tr><tr><td><div><div><p>MULE-18208</p></div></div></td><td><div><div><p>When resolving dependencies, a mule-service no longer includes the Test scope dependencies, which caused unnecessary service registrations.</p></div></div></td></tr><tr><td><div><div><p>MULE-18196</p></div></div></td><td><div><div><p>An application no longer fails to deploy if it has the same custom namespace as that of an applied custom policy.</p></div></div></td></tr><tr><td><div><div><p>MULE-18179</p></div></div></td><td><div><div><p>Resolved a possible stack overflow on <code>RejectionCallbackExecutorServiceDecorator</code> while trying to generate an XML response.</p></div></div></td></tr><tr><td><div><div><p>MULE-18102</p></div></div></td><td><div><div><p>Resolved concurrent subflow instantiation problem where the inner processors location was being corrupted.</p></div></div></td></tr><tr><td><div><div><p>MULE-16668</p></div></div></td><td><div><div><p>Optimized connection-pool validations to avoid excessive and costly checks.</p></div></div></td></tr><tr><td><div><div><p>EE-7097</p></div></div></td><td><div><div><p>Batch job summary is no longer incorrectly logged twice.</p></div></div></td></tr><tr><td><div><div><p>MULE-18310</p></div></div></td><td><div><div><p>Optimized application deployments, resulting in performance improvements.</p></div></div></td></tr><tr><td><div><div><p>MULE-18205</p></div></div></td><td><div><div><p>Optimized <code>FlowProcessMediator#policySuccessError</code> to now create a single router for all exceptions rather than one for each exception or error.</p></div></div></td></tr><tr><td><div><div><p>MULE-18172</p></div></div></td><td><div><div><p>Fixed <code>ObjectStoreToMapAdapter</code> thrown exceptions when used or accessed concurrently.</p></div></div></td></tr><tr><td><div><div><p>MULE-18202</p></div></div></td><td><div><div><p>Upgraded groovy dependency to version 3.0.2.</p></div></div></td></tr><tr><td><div><div><p>SE-15904</p></div></div></td><td><div><div><p>Fixed an issue in which DataWeave’s common subexpression elimination incorrectly reduced two expressions, ignoring middle nodes.</p></div></div></td></tr><tr><td><div><div><p>SE-13691</p></div></div></td><td><div><div><p>Fixed an issue in which the Scheduler incorrectly ran twice.</p></div></div></td></tr><tr><td><div><div><p>MULE-18369</p></div></div></td><td><div><div><p>Fixed an overload error that occurred when an API had a combination of two policies using caching and error-handler components.</p></div></div></td></tr></tbody></table>

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

## April 30, 2020

The initial 4.3.0 release includes new features, fixes, and some known limitations.

### New Features and Enhancements

Mule 4.3.0 introduces several features and enhancements.

#### API Gateway

API Gateway now includes a `disable Policies` annotation. Setting it to `true` enables you to block
the application of policies to the requestor.

In addition, the release introduces several enhancements to resiliency, including a better backoff
mechanism and improvements of the policy deployer mechanism.

#### DataWeave

DataWeave introduces the following:

- `update` operator:  
  Creating modified versions of objects and arrays is now easier. The `update` operator enables you
  to select specific fields to change without changing others.

- Streaming features and enhancements:

  - The XML reader now supports streaming.

  - The JSON reader now supports streaming for more than arrays.

- Literal types:  
  `String`, `Boolean`, and `Number` values can now be handled as literal types, which enables the
  definition of enumerations (Enums) and makes function overloading more dynamic.

- `Period` and `DateTime` consistency:  
  This feature adds an easy way to operate with periods, transform the result into different units,
  and decompose the period into its different parts.

  `Period` changes its behavior for dates in version 2.3.0. To restore the 2.2.0 behavior, set the
  `-M-Dcom.mulesoft.dw.date_minus_back_compatibility=true`. See
  [Add and Subtract Time](https://docs.mulesoft.com/dataweave/2.3/dataweave-cookbook-add-and-subtract-time) for
  additional details.

- DataWeave modules:

  - The new Types module enables type introspection at runtime.

  - DataWeave also introduces a number of new functions in existing modules.

  - Deprecated functions and replacements:  
    The `entrySet`, `keySet`, `nameSet`, `valueSet` functions in the Objects module are deprecated
    in this release and replaced with the functions `entriesOf`, `keysOf`, `namesOf`, `valuesOf` in
    the Core module.

  - `withMaxSize` function:  
    The Strings module has a new function that enables you to specify a maximum size for a given
    value. A value that exceeds the size limit will be truncated. If the size is no greater than the
    limit, the value remains the same.

  - `takeWhile` function:  
    The Objects module has a new function that iterates over the items in an array items while a
    condition is true.

  - `dropWhile` function:  
    The Objects module has a new function that iterates over and ignores the items in an array until
    the specified condition is true.

  - Reader and Writer properties:  
    DataWeave introduces a number of new and enhanced reader and writer properties for supported
    DataWeave formats.

- Custom MIME types:  
  This feature adds a way to define the output MIME type separately from the output data format. It
  also provides a simpler way of defining output and input formats.

- Intersection type:  
  DataWeave introduces the `Intersection` type. The intersection type appends `Object` types. The
  type takes the form `TypeA & TypeB & …​`.

- Performance:  
  DataWeave performance is improved for memory usage, functions (like `groupBy`), and the internal
  execution engine. Improvements include:

  - Common Subexp Elimination  
    To optimize scripts, DataWeave now eliminates common subexpressions by internally using implicit
    variables for them, meaning the subexpressions are only executed once regardless of how many
    times they are repeated.

  - Memory Service:  
    Memory management is now centralized. Several memory management strategies are included, such as
    pooling direct memory or using heap memory exclusively.

- Improvements to parsing error messages:  
  Parsing errors now reflect more accurately missing tokens, incomplete definitions, and other
  common issues. Tips and examples of how to solve the issues are also included.

For more detailed information about these changes, see
[What’s New in Mule 4.3](https://docs.mulesoft.com/mule-runtime/4.3/whats-new-in-mule#dataweave).

#### Core Components

The following Core components have new features in this release.

- Until Successful component:  
  Max Retries (`maxRetries`) and Milliseconds Between Retries (`millisBetweenRetries`) now support a
  number or an expression that resolves to a number.

- Batch Aggregator component:  
  This component adds the `preserveMimeTypes` attribute to makes it easier to handle records from a
  payload that is in a structured text format, such as JSON or XML.

For more detailed information about these changes, see
[What’s New in Mule 4.3](https://docs.mulesoft.com/mule-runtime/4.3/whats-new-in-mule#core_components).

### Changes

- Threading Model

  - The three main thread pools have been combined into one unique thread pool.

  - You can select between the UBER pool strategy (default) or the DEDICATED pools strategy
    (legacy).

  - You can still customize the thread pools' configuration if necessary.

  - If you are upgrading from earlier Mule 4.x versions, see
    [Upgrading from Mule 4.2/4.1](https://docs.mulesoft.com/mule-runtime/4.3/execution-engine#upgrading-from-4-x)

For more detailed information about this change, see
[What’s New in Mule 4.3](https://docs.mulesoft.com/mule-runtime/4.3/whats-new-in-mule#threading_model).

- Performance updates

  Mule 4.3.0 includes several updates to improve performance. Some processes are pre-calculated to
  reduce latency and increase throughput. However, these modifications cause a slight increase in
  memory consumption for Mule components.

  The increase is particularly important when using subflows because the content of a subflow
  replaces each Flow Reference component that references the subflow, causing several instances of
  the event processors inside a subflow to exist in the application at runtime. See
  [Using Subflows](https://docs.mulesoft.com/mule-runtime/4.3/about-flows#using-subflows) for additional details about
  subflow behavior.

For more detailed information about optimizing application performance, see
[Performance Tuning Guide](https://docs.mulesoft.com/mule-runtime/4.3/tuning-guide).

### Upgrade Requirements

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>MULE-16681</p></div></div></td><td><div><div><p>Updated cipher suites for FIPS140-2 mode (check tls-fips140-2.conf file)</p></div></div></td></tr><tr><td><div><div><p>MULE-15596</p></div></div></td><td><div><div><p>Added support to Error Handler for "when" filtering for a certain "type". Before 4.3.0 Setting "when" and "type" simple ignores "when" expression</p></div></div></td></tr><tr><td><div><div><p>MULE-17800</p></div></div></td><td><div><div><p>ParseTemplateProcessor Type Inconsistencies when setting target and target variable</p></div></div></td></tr><tr><td><div><div><p>MULE-17472</p></div></div></td><td><div><div><p>Use of backslash before Properties escapes the evaluation of them. To have the same behavior as before (backslash being a simple character) add the system property <code>mule.properties.correct.backslash.use=false</code></p></div></div></td></tr></tbody></table>

### Known Limitations and Workarounds

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>MULE-18369</p></div></div></td><td><div><div><p>API fails when it applies the Caching Policy before the Message Logging Policy or Header Injection Policy.</p></div></div></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p>MULE-18305</p></div></div></td><td><div><div><p>XmlSdkConfigurationInstance does not delegate methods</p></div></div></td></tr><tr><td><div><div><p>MULE-18304</p></div></div></td><td><div><div><p>NPE in operations within dynamically invoked <code>sub-flow</code></p></div></div></td></tr><tr><td><div><div><p>MULE-18299</p></div></div></td><td><div><div><p>Unexpected run/debug behavior - Flow was terminated abnormally</p></div></div></td></tr><tr><td><div><div><p>MULE-18295</p></div></div></td><td><div><div><p>Performance overhead in SdkInternalContext#locationSpecificContext</p></div></div></td></tr><tr><td><div><div><p>MULE-18286</p></div></div></td><td><div><div><p>Error mappings not honored while running application on LazyInit</p></div></div></td></tr><tr><td><div><div><p>MULE-18281</p></div></div></td><td><div><div><p>ArtifactAstDependencyGraph is not taking configRef parameters into account</p></div></div></td></tr><tr><td><div><div><p>MULE-18276</p></div></div></td><td><div><div><p>IllegalStateException cannot be cast to EventProcessingException</p></div></div></td></tr><tr><td><div><div><p>MULE-18269</p></div></div></td><td><div><div><p>XML SDK variables are sent as null with 4.3.0-RC2</p></div></div></td></tr><tr><td><div><div><p>MULE-18261</p></div></div></td><td><div><div><p>Processed wrapped in a Mono should always recognize itself with a child context</p></div></div></td></tr><tr><td><div><div><p>MULE-18259</p></div></div></td><td><div><div><p>Smart connector fails if http protocol is not defined for a config that contains another http config</p></div></div></td></tr><tr><td><div><div><p>MULE-18248</p></div></div></td><td><div><div><p>Illegal type name exception in AIX OS using JDK8</p></div></div></td></tr><tr><td><div><div><p>MULE-18240</p></div></div></td><td><div><div><p>Scatter Gather resulting in Exception reached PS subscriber for flow</p></div></div></td></tr><tr><td><div><div><p>MULE-18238</p></div></div></td><td><div><div><p>XmlSdkConfigurationProvider does not propagate Lifecycle methods</p></div></div></td></tr><tr><td><div><div><p>MULE-18236</p></div></div></td><td><div><div><p>Getting IndexOutOfBoundsException error for a mapping that works in 4.2.2</p></div></div></td></tr><tr><td><div><div><p>MULE-18234</p></div></div></td><td><div><div><p>App returns correct results, but "Test Connection" FAILS</p></div></div></td></tr><tr><td><div><div><p>MULE-18227</p></div></div></td><td><div><div><p>NPE with scatter-gather within parallel-foreach</p></div></div></td></tr><tr><td><div><div><p>MULE-18200</p></div></div></td><td><div><div><p>4.3.0: readUrl getting blocked when file resource is not present</p></div></div></td></tr><tr><td><div><div><p>MULE-18197</p></div></div></td><td><div><div><p>MUnit test fails when executing XML SDK module</p></div></div></td></tr><tr><td><div><div><p>MULE-18189</p></div></div></td><td><div><div><p>Interception API: Context Id are swapped for processors in scatter-gather</p></div></div></td></tr><tr><td><div><div><p>MULE-18183</p></div></div></td><td><div><div><p>Race condition on ProcessingStrategy#dispose</p></div></div></td></tr><tr><td><div><div><p>MULE-18178</p></div></div></td><td><div><div><p>Max Concurrency not honored in <code>flow-ref</code></p></div></div></td></tr><tr><td><div><div><p>MULE-18177</p></div></div></td><td><div><div><p>Add current location to thread names</p></div></div></td></tr><tr><td><div><div><p>MULE-18164</p></div></div></td><td><div><div><p>Async scope not deploying in a policy</p></div></div></td></tr><tr><td><div><div><p>MULE-18161</p></div></div></td><td><div><div><p>Simple async operation not working</p></div></div></td></tr><tr><td><div><div><p>MULE-18157</p></div></div></td><td><div><div><p>Event modifications lost when setting a securityContext</p></div></div></td></tr><tr><td><div><div><p>MULE-18155</p></div></div></td><td><div><div><p>Dynamic flow-ref must explicitly expect a String on the expressionLanguage</p></div></div></td></tr><tr><td><div><div><p>MULE-18148</p></div></div></td><td><div><div><p>Memory leak on transactional try with error handlers</p></div></div></td></tr><tr><td><div><div><p>MULE-18145</p></div></div></td><td><div><div><p>Operation policies are not applied to requester when it is inside XML Connector</p></div></div></td></tr><tr><td><div><div><p>MULE-18140</p></div></div></td><td><div><div><p>PlatformManaged connection providers do not inject the config name to its delegate</p></div></div></td></tr><tr><td><div><div><p>MULE-18138</p></div></div></td><td><div><div><p>Every time a connection is created/autowired, its class is looked up in the app classloader</p></div></div></td></tr><tr><td><div><div><p>MULE-18129</p></div></div></td><td><div><div><p>Extensions-client times out operations after 5 seconds</p></div></div></td></tr><tr><td><div><div><p>MULE-18124</p></div></div></td><td><div><div><p>When an Exception is raised from a non-blocking SDK operation, an unexpected error is thrown</p></div></div></td></tr><tr><td><div><div><p>MULE-18123</p></div></div></td><td><div><div><p>Source not being intercepted when exception in smart connector</p></div></div></td></tr><tr><td><div><div><p>MULE-18115</p></div></div></td><td><div><div><p>Lazy init: Object store already defined with inline IdempotentRedeliveryPolicy</p></div></div></td></tr><tr><td><div><div><p>MULE-18094</p></div></div></td><td><div><div><p>Pooled Platform Managed Connection Providers fail to be created</p></div></div></td></tr><tr><td><div><div><p>MULE-18093</p></div></div></td><td><div><div><p>Add process id to the start up splash</p></div></div></td></tr><tr><td><div><div><p>MULE-18090</p></div></div></td><td><div><div><p>Flow stuck on JMS publish when connector trows an error</p></div></div></td></tr><tr><td><div><div><p>MULE-18089</p></div></div></td><td><div><div><p>Flow source stopped event if it was not started because of a ComponentInitialStateManager</p></div></div></td></tr><tr><td><div><div><p>MULE-18087</p></div></div></td><td><div><div><p>Processing strategy not propagated to chains of scopes in policies</p></div></div></td></tr><tr><td><div><div><p>MULE-18081</p></div></div></td><td><div><div><p>Remove scheduler warning</p></div></div></td></tr><tr><td><div><div><p>MULE-18078</p></div></div></td><td><div><div><p>DefaultExecutionContext constructor has too much performance overhead</p></div></div></td></tr><tr><td><div><div><p>MULE-18077</p></div></div></td><td><div><div><p>Performance issues with functional idioms</p></div></div></td></tr><tr><td><div><div><p>MULE-18076</p></div></div></td><td><div><div><p>Processing strategy not propagated to sub-flow</p></div></div></td></tr><tr><td><div><div><p>MULE-18073</p></div></div></td><td><div><div><p>Value is not being stored in queue</p></div></div></td></tr><tr><td><div><div><p>MULE-18064</p></div></div></td><td><div><div><p>Subscription context not propagated to error handlers</p></div></div></td></tr><tr><td><div><div><p>MULE-18059</p></div></div></td><td><div><div><p>Flow in initial state stopped is started when app is stopped and started</p></div></div></td></tr><tr><td><div><div><p>MULE-18040</p></div></div></td><td><div><div><p>Scatter-Gather router does not honor route order in aggregated response hashmap when there are 12 or more routes defined</p></div></div></td></tr><tr><td><div><div><p>MULE-18036</p></div></div></td><td><div><div><p>Error raised with incorrect type</p></div></div></td></tr><tr><td><div><div><p>MULE-18030</p></div></div></td><td><div><div><p>HttpPolicyPointcutParameters, only use the headers if a pointcut actually needs them</p></div></div></td></tr><tr><td><div><div><p>MULE-18025</p></div></div></td><td><div><div><p>OutOfMemoryError on multiple policy redeploys</p></div></div></td></tr><tr><td><div><div><p>MULE-18020</p></div></div></td><td><div><div><p>Fix reconnection for Paged Operations that fail after the first page.</p></div></div></td></tr><tr><td><div><div><p>MULE-18010</p></div></div></td><td><div><div><p>Spike: Use generated bytecode instead of reflection to invoke operations</p></div></div></td></tr><tr><td><div><div><p>MULE-18004</p></div></div></td><td><div><div><p>Make constants in <code>AbstractComponent</code> final</p></div></div></td></tr><tr><td><div><div><p>MULE-17994</p></div></div></td><td><div><div><p>Allow policy dispose to finish inflight events</p></div></div></td></tr><tr><td><div><div><p>MULE-17993</p></div></div></td><td><div><div><p>Response callback not called when source policy fails with <code>Source policy already disposed</code></p></div></div></td></tr><tr><td><div><div><p>MULE-17992</p></div></div></td><td><div><div><p>MTF test timeout when two flow-ref are used</p></div></div></td></tr><tr><td><div><div><p>MULE-17987</p></div></div></td><td><div><div><p>Error when logging error for component with special characters in password</p></div></div></td></tr><tr><td><div><div><p>MULE-17975</p></div></div></td><td><div><div><p>Paging Provider is closed twice when it returns an empty page on the first call to getPage.</p></div></div></td></tr><tr><td><div><div><p>MULE-17970</p></div></div></td><td><div><div><p>Reduce verbosity of SpringRegistry</p></div></div></td></tr><tr><td><div><div><p>MULE-17952</p></div></div></td><td><div><div><p>Race condition when cloning a DefaultFlowCallStack</p></div></div></td></tr><tr><td><div><div><p>MULE-17950</p></div></div></td><td><div><div><p>For multi level metadata, same values are retrieved even when changing key parts on SOAP connectors</p></div></div></td></tr><tr><td><div><div><p>MULE-17942</p></div></div></td><td><div><div><p>Connection is not closed during Connection Exceptions on Paged Operations.</p></div></div></td></tr><tr><td><div><div><p>MULE-17939</p></div></div></td><td><div><div><p>Operation considers applied policies regarding thread switches</p></div></div></td></tr><tr><td><div><div><p>MULE-17933</p></div></div></td><td><div><div><p>PersistentXaTransactionContext#poll not honoring timeout</p></div></div></td></tr><tr><td><div><div><p>MULE-17929</p></div></div></td><td><div><div><p>Thread stucks when undeploying a failing operation policy</p></div></div></td></tr><tr><td><div><div><p>MULE-17917</p></div></div></td><td><div><div><p>Missing LegacyConnector class in the compatibility module.</p></div></div></td></tr><tr><td><div><div><p>MULE-17916</p></div></div></td><td><div><div><p>Error on returning a CoreEvent from Soapkit executor</p></div></div></td></tr><tr><td><div><div><p>MULE-17911</p></div></div></td><td><div><div><p>Application logging "FlowStack : &lt;empty&gt; " when LoggerContext.updateLoggers() is called</p></div></div></td></tr><tr><td><div><div><p>MULE-17908</p></div></div></td><td><div><div><p>Missing element in xsd for compatibility plugin</p></div></div></td></tr><tr><td><div><div><p>MULE-17906</p></div></div></td><td><div><div><p>Missing configuration for ConfigOverride parameter with implicit configuration</p></div></div></td></tr><tr><td><div><div><p>MULE-17905</p></div></div></td><td><div><div><p>OAuth token is not refreshed when a paged operation throws the exception when obtaining the second page.</p></div></div></td></tr><tr><td><div><div><p>MULE-17904</p></div></div></td><td><div><div><p>Policy <code>execute-next</code> throws error when inside transactional <code>try</code></p></div></div></td></tr><tr><td><div><div><p>MULE-17903</p></div></div></td><td><div><div><p>CursorProvider not resolved for Object type parameters</p></div></div></td></tr><tr><td><div><div><p>MULE-17902</p></div></div></td><td><div><div><p>Version is not compliant with Semver 2.0</p></div></div></td></tr><tr><td><div><div><p>MULE-17901</p></div></div></td><td><div><div><p>AbstractCursorStreamProviderFactory class cast Exception</p></div></div></td></tr><tr><td><div><div><p>MULE-17888</p></div></div></td><td><div><div><p>ChoiceRouterObjectFactory is not aware of MuleContexts without validations</p></div></div></td></tr><tr><td><div><div><p>MULE-17885</p></div></div></td><td><div><div><p>DataWeave EL should not be lazy when not in tooling mode</p></div></div></td></tr><tr><td><div><div><p>MULE-17883</p></div></div></td><td><div><div><p>ParameterResolvers initialize a new AttributeEvaluator on each execution</p></div></div></td></tr><tr><td><div><div><p>MULE-17882</p></div></div></td><td><div><div><p>NoSuchBeanDefinitionException: No qualifying bean of type 'org.mule.runtime.extension.api.client.ExtensionsClient' when deploying a domain with a configuration for WSC</p></div></div></td></tr><tr><td><div><div><p>MULE-17874</p></div></div></td><td><div><div><p>SDK Should not reject dynamic metadata resolution when an optional key is null</p></div></div></td></tr><tr><td><div><div><p>MULE-17863</p></div></div></td><td><div><div><p>Avoid file leak in TlsConfiguration</p></div></div></td></tr><tr><td><div><div><p>MULE-17862</p></div></div></td><td><div><div><p>Avoid file leak in ParseTemplateProcessor</p></div></div></td></tr><tr><td><div><div><p>MULE-17856</p></div></div></td><td><div><div><p>Large overhead at ExecutionMediator</p></div></div></td></tr><tr><td><div><div><p>MULE-17849</p></div></div></td><td><div><div><p>Flow’s error response builder being executed twice</p></div></div></td></tr><tr><td><div><div><p>MULE-17845</p></div></div></td><td><div><div><p>NPE on MuleArtifactContext#resolveErrorType while resolving empty raise-error element</p></div></div></td></tr><tr><td><div><div><p>MULE-17843</p></div></div></td><td><div><div><p>When smart connector in a policy has a parameter with an invalid DW, it hangs</p></div></div></td></tr><tr><td><div><div><p>MULE-17833</p></div></div></td><td><div><div><p>Contention when instantiating a FileStoreInputStreamBuffer</p></div></div></td></tr><tr><td><div><div><p>MULE-17832</p></div></div></td><td><div><div><p>Flow’s error response builder being executed when a policy fails</p></div></div></td></tr><tr><td><div><div><p>MULE-17819</p></div></div></td><td><div><div><p>ComponentLocationVisitor creates wrong Locations for Connections</p></div></div></td></tr><tr><td><div><div><p>MULE-17814</p></div></div></td><td><div><div><p>Infinite Loop when setting -Dmule.classloading.verbose=true</p></div></div></td></tr><tr><td><div><div><p>MULE-17813</p></div></div></td><td><div><div><p>SourcePolicyContext is created and added even if no policies apply</p></div></div></td></tr><tr><td><div><div><p>MULE-17812</p></div></div></td><td><div><div><p>Refresh Dance not executed after TokenExpiredException</p></div></div></td></tr><tr><td><div><div><p>MULE-17800</p></div></div></td><td><div><div><p>ParseTemplateProcessor Type Inconsistencies when setting target and target variable</p></div></div></td></tr><tr><td><div><div><p>MULE-17791</p></div></div></td><td><div><div><p>Unneficient copying of variables and internal params in EventBuilder</p></div></div></td></tr><tr><td><div><div><p>MULE-1778]</p></div></div></td><td><div><div><p>Add a compile() method on the ExpressionLanguage</p></div></div></td></tr><tr><td><div><div><p>MULE-17770</p></div></div></td><td><div><div><p>Allow UTF-8 in disposition content headers for http request</p></div></div></td></tr><tr><td><div><div><p>MULE-17766</p></div></div></td><td><div><div><p>Race condition on recursive check in flowRef with scatterGather</p></div></div></td></tr><tr><td><div><div><p>MULE-17765</p></div></div></td><td><div><div><p>Validation module does not map MULE:EXPRESSION errors to custom application errors and error logging differs when error is raised in sub-flow</p></div></div></td></tr><tr><td><div><div><p>MULE-17763</p></div></div></td><td><div><div><p>Excesive contention on CursorManager#manage()</p></div></div></td></tr><tr><td><div><div><p>MULE-17762</p></div></div></td><td><div><div><p>MuleContext.getSecurityManager() accesses the registry on every invocation</p></div></div></td></tr><tr><td><div><div><p>MULE-17754</p></div></div></td><td><div><div><p><code>NoSuchElementException</code> when using TransformationService with global errorHandler</p></div></div></td></tr><tr><td><div><div><p>MULE-17750</p></div></div></td><td><div><div><p>High contention on streaming ByteBuffer pool</p></div></div></td></tr><tr><td><div><div><p>MULE-17747</p></div></div></td><td><div><div><p>Event context termination callbacks not called on some situations</p></div></div></td></tr><tr><td><div><div><p>MULE-17741</p></div></div></td><td><div><div><p>FirstSuccessful implementation is blocking</p></div></div></td></tr><tr><td><div><div><p>MULE-17730</p></div></div></td><td><div><div><p>Fix lazyinit for email config in a domain</p></div></div></td></tr><tr><td><div><div><p>MULE-17726</p></div></div></td><td><div><div><p>LazyMuleArtifactContext is not disposing correctly components</p></div></div></td></tr><tr><td><div><div><p>MULE-17725</p></div></div></td><td><div><div><p>DomainClassLoaderFactory doesn’t remove cached class loaders on dispose</p></div></div></td></tr><tr><td><div><div><p>MULE-17698</p></div></div></td><td><div><div><p>OAuth 2 Client Credentials not resolving dynamic metadata</p></div></div></td></tr><tr><td><div><div><p>MULE-17696</p></div></div></td><td><div><div><p>Optional ParameterGroups are required to be exported</p></div></div></td></tr><tr><td><div><div><p>MULE-17692</p></div></div></td><td><div><div><p>TypedValue throws NPE when calling .toString() on null value.</p></div></div></td></tr><tr><td><div><div><p>MULE-17689</p></div></div></td><td><div><div><p>DefaultMetadataCacheManager is not reusing the ObjectStore partition</p></div></div></td></tr><tr><td><div><div><p>MULE-17686</p></div></div></td><td><div><div><p>NPE when stream is remanaged after previous managing decorator is collected</p></div></div></td></tr><tr><td><div><div><p>MULE-17671</p></div></div></td><td><div><div><p>NPE in Policy is producing mule to hang</p></div></div></td></tr><tr><td><div><div><p>MULE-17668</p></div></div></td><td><div><div><p>AST: Ref parameters with <code>null</code> values are marked as missing dependencies</p></div></div></td></tr><tr><td><div><div><p>MULE-17661</p></div></div></td><td><div><div><p>NPE when trying to retrieve metadata using JMS connector</p></div></div></td></tr><tr><td><div><div><p>MULE-17659</p></div></div></td><td><div><div><p>Custom Configuration Properties' parameters cannot depend on Deployment Properties</p></div></div></td></tr><tr><td><div><div><p>MULE-17588</p></div></div></td><td><div><div><p>Lazy init: &lt;notifications ..&gt; component not being initialized</p></div></div></td></tr><tr><td><div><div><p>MULE-17560</p></div></div></td><td><div><div><p>DefaultPersistentMetadataCacheManager is created per application context therefore the shared OS partitioned fails with concurrency</p></div></div></td></tr><tr><td><div><div><p>MULE-17541</p></div></div></td><td><div><div><p>Lazy init: &lt;object class="…​" '/&gt; not lazy initialized</p></div></div></td></tr><tr><td><div><div><p>MULE-17530</p></div></div></td><td><div><div><p>Remove flatMap from CompositeOperationPolicy#applyNextOperation</p></div></div></td></tr><tr><td><div><div><p>MULE-17529</p></div></div></td><td><div><div><p>Remove String.format from PolicyEventMapper</p></div></div></td></tr><tr><td><div><div><p>MULE-17524</p></div></div></td><td><div><div><p>Set instead of List generating inconsistencies resolving dependencies</p></div></div></td></tr><tr><td><div><div><p>MULE-17522</p></div></div></td><td><div><div><p>Fix case for domains in LazyInit on AST</p></div></div></td></tr><tr><td><div><div><p>MULE-17521</p></div></div></td><td><div><div><p>Avoid using an <code>AutoCloseInputStream</code> for streams</p></div></div></td></tr><tr><td><div><div><p>MULE-17518</p></div></div></td><td><div><div><p>Don’t generate schemas in test runner</p></div></div></td></tr><tr><td><div><div><p>MULE-17517</p></div></div></td><td><div><div><p>Source onTerminate callback should run on its own scheduler</p></div></div></td></tr><tr><td><div><div><p>MULE-17515</p></div></div></td><td><div><div><p>Create corrupted files directory before attempting to move files</p></div></div></td></tr><tr><td><div><div><p>MULE-17510</p></div></div></td><td><div><div><p>MetadataOutputDelegate always setting isDynamic to false for MetadataAttributes</p></div></div></td></tr><tr><td><div><div><p>MULE-17507</p></div></div></td><td><div><div><p>Remove unused legacy processing strategies</p></div></div></td></tr><tr><td><div><div><p>MULE-17505</p></div></div></td><td><div><div><p>Runtime is not starting ConnectionProviders during metadata resolution phase</p></div></div></td></tr><tr><td><div><div><p>MULE-17486</p></div></div></td><td><div><div><p>System.gc() called multiple times when disposing ClassLoaders</p></div></div></td></tr><tr><td><div><div><p>MULE-17480</p></div></div></td><td><div><div><p>Http requester can’t handle large headers in Mule 4</p></div></div></td></tr><tr><td><div><div><p>MULE-17472</p></div></div></td><td><div><div><p>Configuration property output not correct when prefix is escaped</p></div></div></td></tr><tr><td><div><div><p>MULE-17466</p></div></div></td><td><div><div><p>Maps should not be required to have getters</p></div></div></td></tr><tr><td><div><div><p>MULE-17451</p></div></div></td><td><div><div><p>Top level object stores should be started sooner</p></div></div></td></tr><tr><td><div><div><p>MULE-17449</p></div></div></td><td><div><div><p>ManagedCursors allow access to unmanaged provider</p></div></div></td></tr><tr><td><div><div><p>MULE-17431</p></div></div></td><td><div><div><p>ExtensionMessageSource requires FlowConstruct to be root element</p></div></div></td></tr><tr><td><div><div><p>MULE-17429</p></div></div></td><td><div><div><p>Workaround for MMP-499 in runtime</p></div></div></td></tr><tr><td><div><div><p>MULE-17426</p></div></div></td><td><div><div><p>Stacktrace is logged when undeploying a policy</p></div></div></td></tr><tr><td><div><div><p>MULE-17421</p></div></div></td><td><div><div><p>RoundRobin implementation is blocking</p></div></div></td></tr><tr><td><div><div><p>MULE-17416</p></div></div></td><td><div><div><p>ComponentModel equals/hashCode ignoring location</p></div></div></td></tr><tr><td><div><div><p>MULE-17415</p></div></div></td><td><div><div><p>Polling Sources fail to pick the same item multiple times (Regression)</p></div></div></td></tr><tr><td><div><div><p>MULE-17409</p></div></div></td><td><div><div><p>MetadataCacheIdGenerator for configuration elements is not taking into account parameters and only using DslTagId hash</p></div></div></td></tr><tr><td><div><div><p>MULE-17401</p></div></div></td><td><div><div><p>Scheduler source should route emitted message through FlowProcessMediator</p></div></div></td></tr><tr><td><div><div><p>MULE-17398</p></div></div></td><td><div><div><p>Operations that return a PagingProvider do not populate the type catalog properly</p></div></div></td></tr><tr><td><div><div><p>MULE-17390</p></div></div></td><td><div><div><p>MessageProcessPhase and MessageProcessTemplate are no longer used</p></div></div></td></tr><tr><td><div><div><p>MULE-17386</p></div></div></td><td><div><div><p>CommonSourcePolicy callback invoked twice when event is failed</p></div></div></td></tr><tr><td><div><div><p>MULE-17384</p></div></div></td><td><div><div><p>Extensions maven plugin not honoring extensions dependencies</p></div></div></td></tr><tr><td><div><div><p>MULE-17383</p></div></div></td><td><div><div><p>High CPU usage by VM Listeners with Persistent queues</p></div></div></td></tr><tr><td><div><div><p>MULE-17373</p></div></div></td><td><div><div><p>Final "catch-all" check for error handlers does not account for ANY matcher</p></div></div></td></tr><tr><td><div><div><p>MULE-17362</p></div></div></td><td><div><div><p>Top-level pojos from extensions do not have annotations</p></div></div></td></tr><tr><td><div><div><p>MULE-17359</p></div></div></td><td><div><div><p>CPU Light thread pool exhausted due to a testConnectivity when DynamicConfiguration is created</p></div></div></td></tr><tr><td><div><div><p>MULE-17346</p></div></div></td><td><div><div><p>Move ParameterDslDeclarationEnricher to extensions-api</p></div></div></td></tr><tr><td><div><div><p>MULE-17341</p></div></div></td><td><div><div><p>Referenced subflows are not being started after stop-start the application</p></div></div></td></tr><tr><td><div><div><p>MULE-17333</p></div></div></td><td><div><div><p>Missing hashCode method in TypedValueTypeAnnotation</p></div></div></td></tr><tr><td><div><div><p>MULE-17331</p></div></div></td><td><div><div><p>ParameterGroup with showInDsl property set and isOneRequired fails to instantiate operation</p></div></div></td></tr><tr><td><div><div><p>MULE-17330</p></div></div></td><td><div><div><p>Race condition when the same CursorProvider is managed twice</p></div></div></td></tr><tr><td><div><div><p>MULE-17322</p></div></div></td><td><div><div><p>ComponentResultJsonSerializer uses TCCL to load by SPI type annotations contributed by extensions-api</p></div></div></td></tr><tr><td><div><div><p>MULE-17313</p></div></div></td><td><div><div><p>Transaction began using TryScope are not switching to IO</p></div></div></td></tr><tr><td><div><div><p>MULE-17311</p></div></div></td><td><div><div><p>Services started by an app plugin retain app classloader after reploy/undeploy</p></div></div></td></tr><tr><td><div><div><p>MULE-17307</p></div></div></td><td><div><div><p>MetadataTypes from the extension model have different instances representing the same type</p></div></div></td></tr><tr><td><div><div><p>MULE-17300</p></div></div></td><td><div><div><p>DefaultArchiveDeployer#deployPackagedArtifact doesn’t redeploy when receives an URI</p></div></div></td></tr><tr><td><div><div><p>MULE-17298</p></div></div></td><td><div><div><p>Splash screen does not list odd named patches</p></div></div></td></tr><tr><td><div><div><p>MULE-17296</p></div></div></td><td><div><div><p>CursorProvider wrongly marked as a consumable class</p></div></div></td></tr><tr><td><div><div><p>MULE-17293</p></div></div></td><td><div><div><p>Stereotypes enrichment is done before all types are determined</p></div></div></td></tr><tr><td><div><div><p>MULE-17288</p></div></div></td><td><div><div><p>CacheId for fetching metadata keys should be broader</p></div></div></td></tr><tr><td><div><div><p>MULE-17277</p></div></div></td><td><div><div><p>Websockets dropped after 30 seconds idle</p></div></div></td></tr><tr><td><div><div><p>MULE-17267</p></div></div></td><td><div><div><p>Race condition on source shutdown and restart on connection exception</p></div></div></td></tr><tr><td><div><div><p>MULE-17264</p></div></div></td><td><div><div><p>Reintroduce the event buffering when dispatching to a flow</p></div></div></td></tr><tr><td><div><div><p>MULE-17250</p></div></div></td><td><div><div><p>POC on Remove <code>flatMap</code> in ModuleFlowProcessingPhase$FlowProcessor</p></div></div></td></tr><tr><td><div><div><p>MULE-17240</p></div></div></td><td><div><div><p>MultiMap is losing the order when converting to ImmutableMultiMap</p></div></div></td></tr><tr><td><div><div><p>MULE-17225</p></div></div></td><td><div><div><p>Loader constraint violation when trying to deploy application.</p></div></div></td></tr><tr><td><div><div><p>MULE-17223</p></div></div></td><td><div><div><p>MuleApp with Salesforce Connector leaking MuleApplicationClassLoader after undeploy or hotdeploy</p></div></div></td></tr><tr><td><div><div><p>MULE-17218</p></div></div></td><td><div><div><p>Mule SDK is leaking extensions configurations over the time</p></div></div></td></tr><tr><td><div><div><p>MULE-17210</p></div></div></td><td><div><div><p>Too many ephemeral events are created just to set a variable</p></div></div></td></tr><tr><td><div><div><p>MULE-17182</p></div></div></td><td><div><div><p>CursorProvider set in variables are not managed</p></div></div></td></tr><tr><td><div><div><p>MULE-17168</p></div></div></td><td><div><div><p>Remove softreferences for app classloaders to avoid OOM on redeploy</p></div></div></td></tr><tr><td><div><div><p>MULE-17166</p></div></div></td><td><div><div><p>Wrong group id for HTTP Connector in BundlePluginDependenciesResolver</p></div></div></td></tr><tr><td><div><div><p>MULE-17112</p></div></div></td><td><div><div><p>Internal libraries of a plugin are overridden by a sharedLib fron an app</p></div></div></td></tr><tr><td><div><div><p>MULE-17110</p></div></div></td><td><div><div><p>NTLM authentication with dynamic credentials is successful despite credentials changes</p></div></div></td></tr><tr><td><div><div><p>MULE-17105</p></div></div></td><td><div><div><p>Typo in 'secutiry' package</p></div></div></td></tr><tr><td><div><div><p>MULE-17096</p></div></div></td><td><div><div><p>NullPointerException when lazy initializing subflow with async scope</p></div></div></td></tr><tr><td><div><div><p>MULE-17091</p></div></div></td><td><div><div><p>Object streams not automatically closed if &lt;non-repeatable-iterable&gt; option is selected</p></div></div></td></tr><tr><td><div><div><p>MULE-17082</p></div></div></td><td><div><div><p>Race condition on test connectivity while deploying applications</p></div></div></td></tr><tr><td><div><div><p>MULE-17081</p></div></div></td><td><div><div><p>PipelineMessageNotificationListener returns a PipelineMessageNotification with null event when an exception is raised in the Mule flow.</p></div></div></td></tr><tr><td><div><div><p>MULE-17077</p></div></div></td><td><div><div><p>PersistentQueueTransactionContext#poll not honoring timeout</p></div></div></td></tr><tr><td><div><div><p>MULE-17065</p></div></div></td><td><div><div><p>Scatter gather and Parallel Foreach are not working inside error handler</p></div></div></td></tr><tr><td><div><div><p>MULE-17061</p></div></div></td><td><div><div><p>Optimization to avoid thread switch in PS is broken</p></div></div></td></tr><tr><td><div><div><p>MULE-17055</p></div></div></td><td><div><div><p>@OutputJsonType doesn’t work correctly with array operations</p></div></div></td></tr><tr><td><div><div><p>MULE-17051</p></div></div></td><td><div><div><p>Default Error Handler should be looked up after initialization</p></div></div></td></tr><tr><td><div><div><p>MULE-17050</p></div></div></td><td><div><div><p>SDK Non Blocking operation and policy is not returning a response under load</p></div></div></td></tr><tr><td><div><div><p>MULE-17048</p></div></div></td><td><div><div><p>Race condition when stopping a flow with an inflight event in an <code>async</code> block</p></div></div></td></tr><tr><td><div><div><p>MULE-17045</p></div></div></td><td><div><div><p>Connections are not closed when streaming operation fails</p></div></div></td></tr><tr><td><div><div><p>MULE-17025</p></div></div></td><td><div><div><p>ErrorHandler raising error not working</p></div></div></td></tr><tr><td><div><div><p>MULE-17023</p></div></div></td><td><div><div><p>Nested Try is rolling back tx created by outer try</p></div></div></td></tr><tr><td><div><div><p>MULE-17022</p></div></div></td><td><div><div><p>Transformation resolver failing to found transformer between byte array and inputStream</p></div></div></td></tr><tr><td><div><div><p>MULE-17019</p></div></div></td><td><div><div><p>Unauthorize operation does not reset ConnectionProviders</p></div></div></td></tr><tr><td><div><div><p>MULE-17007</p></div></div></td><td><div><div><p>@OutputJsonType does not set metadata type id</p></div></div></td></tr><tr><td><div><div><p>MULE-16995</p></div></div></td><td><div><div><p>Shared runtime deps in app mess up classloading</p></div></div></td></tr><tr><td><div><div><p>MULE-16994</p></div></div></td><td><div><div><p>Use of cache instead of WeakHashMap to avoid infinite loop in DefaultLifecycleInterceptor</p></div></div></td></tr><tr><td><div><div><p>MULE-16991</p></div></div></td><td><div><div><p>Race condition when invalidating cached connections</p></div></div></td></tr><tr><td><div><div><p>MULE-16987</p></div></div></td><td><div><div><p>Interception API: Parameters of smart connector not intercepted</p></div></div></td></tr><tr><td><div><div><p>MULE-16986</p></div></div></td><td><div><div><p>XA Transactions fail to rollback on ConnectionException</p></div></div></td></tr><tr><td><div><div><p>MULE-16983</p></div></div></td><td><div><div><p>Reconnection should not retry when resource has joined active transaction</p></div></div></td></tr><tr><td><div><div><p>MULE-16982</p></div></div></td><td><div><div><p>ArrayOutOfBoundException when creating custom scheduler</p></div></div></td></tr><tr><td><div><div><p>MULE-16979</p></div></div></td><td><div><div><p>Review choice</p></div></div></td></tr><tr><td><div><div><p>MULE-16974</p></div></div></td><td><div><div><p>FTP reconnection strategy repeat the "start delay" wait time</p></div></div></td></tr><tr><td><div><div><p>MULE-16965</p></div></div></td><td><div><div><p>MuleRuntimeException when creating namespace for custom error</p></div></div></td></tr><tr><td><div><div><p>MULE-16964</p></div></div></td><td><div><div><p>TryScope with no tx fails within subFlow+async</p></div></div></td></tr><tr><td><div><div><p>MULE-16952</p></div></div></td><td><div><div><p>Publisher returned by applyWithChildContext not completed when source is completed</p></div></div></td></tr><tr><td><div><div><p>MULE-16936</p></div></div></td><td><div><div><p>Mule 4 JMS Bridge (ActiveMQ) scenario stops working after a certain time</p></div></div></td></tr><tr><td><div><div><p>MULE-16920</p></div></div></td><td><div><div><p>"Cannot process event as 'flow' is stopped" when disposing and reinitializing source</p></div></div></td></tr><tr><td><div><div><p>MULE-16899</p></div></div></td><td><div><div><p>ClassCast exception when registry lookup finds no match</p></div></div></td></tr><tr><td><div><div><p>MULE-16896</p></div></div></td><td><div><div><p>Bound connections not released on TransactionException</p></div></div></td></tr><tr><td><div><div><p>MULE-16894</p></div></div></td><td><div><div><p>IllegalStateException in Polling Source when cluste node is shutting down</p></div></div></td></tr><tr><td><div><div><p>MULE-16892</p></div></div></td><td><div><div><p>Error handler being executed twice when flow ref is involved</p></div></div></td></tr><tr><td><div><div><p>MULE-16891</p></div></div></td><td><div><div><p>flowTrace OoM when using foreach with large collections</p></div></div></td></tr><tr><td><div><div><p>MULE-16890</p></div></div></td><td><div><div><p>AdoptJdk shown as un unsupported vendor</p></div></div></td></tr><tr><td><div><div><p>MULE-16889</p></div></div></td><td><div><div><p>DefaultDomainManager#getDomain should retrieve a compatible version of the required domain</p></div></div></td></tr><tr><td><div><div><p>MULE-16878</p></div></div></td><td><div><div><p>StringToEnum Transformer should have different names for each extensionModel</p></div></div></td></tr><tr><td><div><div><p>MULE-16872</p></div></div></td><td><div><div><p>Async in a transaction executes in the same thread as the transaction</p></div></div></td></tr><tr><td><div><div><p>MULE-16856</p></div></div></td><td><div><div><p>Starting a flow should fail when a task is rejected from scheduler.</p></div></div></td></tr><tr><td><div><div><p>MULE-16853</p></div></div></td><td><div><div><p>ConfigurationProperties does not honor properties hierarchy when having prop resolved with placeholder</p></div></div></td></tr><tr><td><div><div><p>MULE-16847</p></div></div></td><td><div><div><p>MessageProcessors.processWithChildContext must complete the EventContext</p></div></div></td></tr><tr><td><div><div><p>MULE-16841</p></div></div></td><td><div><div><p>Password mask regex does not consider dw and non-literal expressions.</p></div></div></td></tr><tr><td><div><div><p>MULE-16837</p></div></div></td><td><div><div><p>[Policy][OAuth] - Timeout and low TPS</p></div></div></td></tr><tr><td><div><div><p>MULE-16836</p></div></div></td><td><div><div><p>Cannot find snapshot artifact via resource loader when trying to scaffold an API</p></div></div></td></tr><tr><td><div><div><p>MULE-16831</p></div></div></td><td><div><div><p>Fix XA transactions with bitronix</p></div></div></td></tr><tr><td><div><div><p>MULE-16830</p></div></div></td><td><div><div><p>Global Properties are taking precedence over Application Properties</p></div></div></td></tr><tr><td><div><div><p>MULE-16824</p></div></div></td><td><div><div><p>LazyInit should initialize the Mule configuration at part of the component initializations phase</p></div></div></td></tr><tr><td><div><div><p>MULE-16817</p></div></div></td><td><div><div><p>Pooled connections are not removed from the pool when they should evict.</p></div></div></td></tr><tr><td><div><div><p>MULE-16790</p></div></div></td><td><div><div><p>Global ErrorHandler does not resolve transaction</p></div></div></td></tr><tr><td><div><div><p>MULE-16786</p></div></div></td><td><div><div><p>Dynamic configurations eviction should consider sources as in-flight operations</p></div></div></td></tr><tr><td><div><div><p>MULE-16784</p></div></div></td><td><div><div><p>MuleClassLoaderLookupPolicy wrongly assumming <code>javax.xml.bind.attachment</code> as system package in Java 11</p></div></div></td></tr><tr><td><div><div><p>MULE-16775</p></div></div></td><td><div><div><p>OnErrorPropagate in global error handler is not rollbacking tx</p></div></div></td></tr><tr><td><div><div><p>MULE-16758</p></div></div></td><td><div><div><p>Multithreaded sources are concurrently reconnected more than once</p></div></div></td></tr><tr><td><div><div><p>MULE-16753</p></div></div></td><td><div><div><p>A transaction is not available error related to execution on a cpuLight thread</p></div></div></td></tr><tr><td><div><div><p>MULE-16744</p></div></div></td><td><div><div><p><code>spring.schemas</code> exported from runtime conflict with spring dependencies used in an app</p></div></div></td></tr><tr><td><div><div><p>MULE-16730</p></div></div></td><td><div><div><p>Interception API: Validation all throws NullPointerException</p></div></div></td></tr><tr><td><div><div><p>MULE-16725</p></div></div></td><td><div><div><p>Fix race condition in flow lifecycle handling</p></div></div></td></tr><tr><td><div><div><p>MULE-16633</p></div></div></td><td><div><div><p>Cool Mulesoft logo in splash screen looking bad in windows</p></div></div></td></tr><tr><td><div><div><p>MULE-16551</p></div></div></td><td><div><div><p>When Policy is present, Event is not serializable</p></div></div></td></tr><tr><td><div><div><p>MULE-16527</p></div></div></td><td><div><div><p>Remove <code>flatMap</code> in UntilSuccesful</p></div></div></td></tr><tr><td><div><div><p>MULE-16463</p></div></div></td><td><div><div><p>Remove <code>flatMap</code> in static &lt;flow-ref&gt;</p></div></div></td></tr><tr><td><div><div><p>MULE-16462</p></div></div></td><td><div><div><p>Remove <code>flatMap</code> in ModuleFlowProcessingPhase$FlowProcessor</p></div></div></td></tr><tr><td><div><div><p>MULE-16461</p></div></div></td><td><div><div><p>Remove <code>concatMap</code> in XML SDK chain execution</p></div></div></td></tr><tr><td><div><div><p>MULE-16285</p></div></div></td><td><div><div><p>Interception API: Smart connectors inside scopes are not skipped properly</p></div></div></td></tr><tr><td><div><div><p>MULE-16141</p></div></div></td><td><div><div><p>SDK is not validating input POJOs to have a default constructor</p></div></div></td></tr><tr><td><div><div><p>MULE-16129</p></div></div></td><td><div><div><p>Cannot deactivate streaming in operations that return lists/maps of streams.</p></div></div></td></tr><tr><td><div><div><p>MULE-15752</p></div></div></td><td><div><div><p>InjectParamsFromContextServiceMethodInvoker makes excessive registry lookups</p></div></div></td></tr><tr><td><div><div><p>MULE-15599</p></div></div></td><td><div><div><p>Serializing an artifact model constructed from serializing a JSON loses data</p></div></div></td></tr><tr><td><div><div><p>MULE-10702</p></div></div></td><td><div><div><p>Remove double check locking: StaticBulkQueryResolver</p></div></div></td></tr><tr><td><div><div><p>MULE-10347</p></div></div></td><td><div><div><p>Generics are not resolved for Map implementations</p></div></div></td></tr><tr><td><div><div><p>EE-7290</p></div></div></td><td><div><div><p>[IBMMQ][Bridge][Daily] TPS Degradation for all IBMMQ_Bridge apps</p></div></div></td></tr><tr><td><div><div><p>EE-7289</p></div></div></td><td><div><div><p>[JMS Bridge] jms_bridge_transactional app TPS lower than 1</p></div></div></td></tr><tr><td><div><div><p>EE-7283</p></div></div></td><td><div><div><p>OCS add system property for setting platfotm authentication url suffix</p></div></div></td></tr><tr><td><div><div><p>EE-7277</p></div></div></td><td><div><div><p>MuleLicenseInterrupter creates a thread named pool-n-thread-m</p></div></div></td></tr><tr><td><div><div><p>EE-7276</p></div></div></td><td><div><div><p>Regression on http connector</p></div></div></td></tr><tr><td><div><div><p>EE-7272</p></div></div></td><td><div><div><p>Cache scope storing unneeded data in the store</p></div></div></td></tr><tr><td><div><div><p>EE-7268</p></div></div></td><td><div><div><p>Possible memory leak when restarting batch applications</p></div></div></td></tr><tr><td><div><div><p>EE-7244</p></div></div></td><td><div><div><p>Getting "Cannot open a new cursor on a closed stream" error when 0 records are being processed</p></div></div></td></tr><tr><td><div><div><p>EE-7243</p></div></div></td><td><div><div><p>Batch Aggregator Out of Memory issue</p></div></div></td></tr><tr><td><div><div><p>EE-7239</p></div></div></td><td><div><div><p>Ambiguous PID when /mule start is Used</p></div></div></td></tr><tr><td><div><div><p>EE-7164</p></div></div></td><td><div><div><p>Batch Engine is no reinitialized in case app is restarted</p></div></div></td></tr><tr><td><div><div><p>EE-7135</p></div></div></td><td><div><div><p>TransactionalWrapper is not setting XAResources that are not DirectXASessions as resources to TransactionalManagerWrapper</p></div></div></td></tr><tr><td><div><div><p>EE-7100</p></div></div></td><td><div><div><p>BTI wrapper not returning XAConnection</p></div></div></td></tr><tr><td><div><div><p>EE-7061</p></div></div></td><td><div><div><p>Lingering Streaming aggregator input queue transactions while reading</p></div></div></td></tr><tr><td><div><div><p>EE-6927</p></div></div></td><td><div><div><p>EE version is loading mule-service-weave and mule-service-weave-ee</p></div></div></td></tr><tr><td><div><div><p>EE-6889</p></div></div></td><td><div><div><p>JdbcMapStore#loadAll(keys) should only load keys passed as parameter</p></div></div></td></tr><tr><td><div><div><p>EE-6866</p></div></div></td><td><div><div><p>When thread waiting in Hz is interrupted, InterruptedException is not thrown immediately</p></div></div></td></tr><tr><td><div><div><p>EE-6860</p></div></div></td><td><div><div><p>Escape table names in Microsoft SQL database store query builder strategy</p></div></div></td></tr><tr><td><div><div><p>EE-6857</p></div></div></td><td><div><div><p>File leak when getting dw file for transformation</p></div></div></td></tr><tr><td><div><div><p>EE-6852</p></div></div></td><td><div><div><p>Unlock hazelcast lock in the same thread where it was locked</p></div></div></td></tr><tr><td><div><div><p>EE-6834</p></div></div></td><td><div><div><p>Http Policy Module has no Extension Model</p></div></div></td></tr><tr><td><div><div><p>EE-6830</p></div></div></td><td><div><div><p>Tracking processors are marked as UNKNOWN instead of OPERATION</p></div></div></td></tr><tr><td><div><div><p>EE-6823</p></div></div></td><td><div><div><p>Automatically undeployed tooling apps are kept on memory for around an hour</p></div></div></td></tr><tr><td><div><div><p>EE-6804</p></div></div></td><td><div><div><p>Bitronix Proxy hides connectivity exceptions</p></div></div></td></tr><tr><td><div><div><p>EE-6797</p></div></div></td><td><div><div><p>Bitronix exception when redeploying an app using XA transactions</p></div></div></td></tr><tr><td><div><div><p>EE-6796</p></div></div></td><td><div><div><p>Dirty Bitronix transaction log</p></div></div></td></tr><tr><td><div><div><p>EE-6780</p></div></div></td><td><div><div><p>Corrupt patches not applied but logged as applied</p></div></div></td></tr><tr><td><div><div><p>EE-6779</p></div></div></td><td><div><div><p>BitronixTransactionManager built before QueueManager initialize causes NPE</p></div></div></td></tr><tr><td><div><div><p>EE-6774</p></div></div></td><td><div><div><p>Memory leak on com.mulesoft.mule.runtime.bti.internal.xa.QueueManagerXaResourceProducer</p></div></div></td></tr><tr><td><div><div><p>EE-6769</p></div></div></td><td><div><div><p>Possible race condition when registering ConnectionFactory in Bitronix</p></div></div></td></tr><tr><td><div><div><p>EE-6710</p></div></div></td><td><div><div><p>Batch RecordFilteringStrategy is not filtering correctly</p></div></div></td></tr><tr><td><div><div><p>EE-6682</p></div></div></td><td><div><div><p>Table name transforms in cluster object store are only working for postgresql</p></div></div></td></tr><tr><td><div><div><p>EE-6574</p></div></div></td><td><div><div><p>Organization credentials and encryption key are displayed in plain text in Cluster splash screen.</p></div></div></td></tr><tr><td><div><div><p>EE-6377</p></div></div></td><td><div><div><p>Batch Aggregator does not support JSON Payload</p></div></div></td></tr><tr><td><div><div><p>EE-6374</p></div></div></td><td><div><div><p>Sending large bodies causes OOM error in HTTP requester</p></div></div></td></tr><tr><td><div><div><p>EE-6338</p></div></div></td><td><div><div><p>A project using Netsuite fails with OOM after a few redeploys</p></div></div></td></tr><tr><td><div><div><p>EE-6108</p></div></div></td><td><div><div><p>Mule 4 Performance degradation on HTTP Proxy Scenarios</p></div></div></td></tr><tr><td><div><div><p>MULE-18288</p></div></div></td><td><div><div><p>Prevent memory leaks from plugins that use scala</p></div></div></td></tr><tr><td><div><div><p>MULE-18262</p></div></div></td><td><div><div><p>Allow to customize the default scheduler fixed frequency through a System Property</p></div></div></td></tr><tr><td><div><div><p>MULE-18141</p></div></div></td><td><div><div><p>Add warnings about not found classes for verbose classloading</p></div></div></td></tr><tr><td><div><div><p>MULE-18127</p></div></div></td><td><div><div><p>Provide a mechanism to disable log separation</p></div></div></td></tr><tr><td><div><div><p>MULE-18050</p></div></div></td><td><div><div><p>Improve performance of binding context</p></div></div></td></tr><tr><td><div><div><p>MULE-18049</p></div></div></td><td><div><div><p>Improve performance of policies lookup when no policies are applied</p></div></div></td></tr><tr><td><div><div><p>MULE-18047</p></div></div></td><td><div><div><p>Add the component that generated a cursor provider</p></div></div></td></tr><tr><td><div><div><p>MULE-18023</p></div></div></td><td><div><div><p>Remove spring repo declaration in poms</p></div></div></td></tr><tr><td><div><div><p>MULE-18021</p></div></div></td><td><div><div><p>Upgrade log4j to 2.13.1</p></div></div></td></tr><tr><td><div><div><p>MULE-18017</p></div></div></td><td><div><div><p>Improve performance of LifecycleFilterProxy</p></div></div></td></tr><tr><td><div><div><p>MULE-17988</p></div></div></td><td><div><div><p>Do not use Optional in Either</p></div></div></td></tr><tr><td><div><div><p>MULE-17985</p></div></div></td><td><div><div><p>Support policy application depending on request headers</p></div></div></td></tr><tr><td><div><div><p>MULE-17935</p></div></div></td><td><div><div><p>Support Platform Managed OAuth tokens in the SDK</p></div></div></td></tr><tr><td><div><div><p>MULE-17910</p></div></div></td><td><div><div><p>Remove <code>distinct</code> from child context processing</p></div></div></td></tr><tr><td><div><div><p>MULE-17909</p></div></div></td><td><div><div><p>Replace calls to <code>flux.mergeWith</code></p></div></div></td></tr><tr><td><div><div><p>MULE-17889</p></div></div></td><td><div><div><p>Support repeatable streaming buffering from an existing file</p></div></div></td></tr><tr><td><div><div><p>MULE-17844</p></div></div></td><td><div><div><p>Remove <code>append-string-transformer</code></p></div></div></td></tr><tr><td><div><div><p>MULE-17829</p></div></div></td><td><div><div><p>MessageProcessorNotification listeners not registered by default</p></div></div></td></tr><tr><td><div><div><p>MULE-17825</p></div></div></td><td><div><div><p>Group error handling internal parameters into unified pojos</p></div></div></td></tr><tr><td><div><div><p>MULE-17805</p></div></div></td><td><div><div><p>Remove child context used in <code>try</code></p></div></div></td></tr><tr><td><div><div><p>MULE-17804</p></div></div></td><td><div><div><p>Remove child contexts uses in policies infrastructure</p></div></div></td></tr><tr><td><div><div><p>MULE-17801</p></div></div></td><td><div><div><p>Improve performance of <code>MetadataType#hashCode</code></p></div></div></td></tr><tr><td><div><div><p>MULE-17780</p></div></div></td><td><div><div><p>Avoid creating an extra intercepting chain when there are no interceptors</p></div></div></td></tr><tr><td><div><div><p>MULE-17757</p></div></div></td><td><div><div><p>Migrate uses of <code>MessagingExceptionResolver#resolve(MessagingException, MuleContext)</code></p></div></div></td></tr><tr><td><div><div><p>MULE-17743</p></div></div></td><td><div><div><p>Remove the use of the eventContext ResponsePublisher</p></div></div></td></tr><tr><td><div><div><p>MULE-17703</p></div></div></td><td><div><div><p>Validate preexisting config-ref parameter on ConfigRefDeclarationEnricher</p></div></div></td></tr><tr><td><div><div><p>MULE-17672</p></div></div></td><td><div><div><p>Make DefaultTypedComponentIdentifier#hashCode consistent across runs</p></div></div></td></tr><tr><td><div><div><p>MULE-17667</p></div></div></td><td><div><div><p>Automatically determine if a parameter is the ComponentId</p></div></div></td></tr><tr><td><div><div><p>MULE-17647</p></div></div></td><td><div><div><p>Allow domains to be redeployed without restarting its stopped applications</p></div></div></td></tr><tr><td><div><div><p>MULE-17536</p></div></div></td><td><div><div><p>FunctionalReadWriteLock: Provide withReadLock methods</p></div></div></td></tr><tr><td><div><div><p>MULE-17535</p></div></div></td><td><div><div><p>Performance improvements for MultiMap immutability</p></div></div></td></tr><tr><td><div><div><p>MULE-17525</p></div></div></td><td><div><div><p>Allow dynamic configuration for the proxy on the HTTP requester</p></div></div></td></tr><tr><td><div><div><p>MULE-17498</p></div></div></td><td><div><div><p>XML SDK: avoid container componentModel modification in config macroexpansion</p></div></div></td></tr><tr><td><div><div><p>MULE-17497</p></div></div></td><td><div><div><p>XML SDK: avoid container componentModel modification in operation macroexpansion</p></div></div></td></tr><tr><td><div><div><p>MULE-17487</p></div></div></td><td><div><div><p>Use OptionalInt instead of Optional&lt;Integer&gt; for building locations</p></div></div></td></tr><tr><td><div><div><p>MULE-17420</p></div></div></td><td><div><div><p>XML SDK: link with the inner models on the xml sdk component definition</p></div></div></td></tr><tr><td><div><div><p>MULE-17417</p></div></div></td><td><div><div><p>Add a method in DeploymentService interface to redeploy applications using a new URI</p></div></div></td></tr><tr><td><div><div><p>MULE-17334</p></div></div></td><td><div><div><p>Add missing exported/imported types in test extensions</p></div></div></td></tr><tr><td><div><div><p>MULE-17281</p></div></div></td><td><div><div><p>SDK needs to allow operations to obtain the effective retry policy</p></div></div></td></tr><tr><td><div><div><p>MULE-17257</p></div></div></td><td><div><div><p>Add more detail to FlowBackpressureException</p></div></div></td></tr><tr><td><div><div><p>MULE-17256</p></div></div></td><td><div><div><p>Add missing stereotypes to tls:context</p></div></div></td></tr><tr><td><div><div><p>MULE-17203</p></div></div></td><td><div><div><p>Properly add doc: attributes as component metadata</p></div></div></td></tr><tr><td><div><div><p>MULE-17185</p></div></div></td><td><div><div><p>Flowref flatmap removal leads to a notorious throughput decrease in the static-flow-ref-subflow case</p></div></div></td></tr><tr><td><div><div><p>MULE-17161</p></div></div></td><td><div><div><p>Allow SDK to specify that certain configs should never be used in an implicit way</p></div></div></td></tr><tr><td><div><div><p>MULE-17114</p></div></div></td><td><div><div><p>Add the notImported information from MULE-17112 into the plugins packager</p></div></div></td></tr><tr><td><div><div><p>MULE-17111</p></div></div></td><td><div><div><p>Create API to propagate a whole custom event when an error occurs in a Processor</p></div></div></td></tr><tr><td><div><div><p>MULE-17079</p></div></div></td><td><div><div><p>Remove flatMap from ProactorStreamProcessingStrategy#proactor</p></div></div></td></tr><tr><td><div><div><p>MULE-17078</p></div></div></td><td><div><div><p>Remove dependency of transactions infrastructure on the MuleContext</p></div></div></td></tr><tr><td><div><div><p>MULE-17066</p></div></div></td><td><div><div><p>ExecutableComponent api should provide a way to mutate the child event that is going to be created</p></div></div></td></tr><tr><td><div><div><p>MULE-17060</p></div></div></td><td><div><div><p>Use the default ProcessingStrategy for policies instead of a custom one</p></div></div></td></tr><tr><td><div><div><p>MULE-17001</p></div></div></td><td><div><div><p>Avoid unneeded message creation in source callback</p></div></div></td></tr><tr><td><div><div><p>MULE-16990</p></div></div></td><td><div><div><p>Improve troubleshooting logging for XA transaction</p></div></div></td></tr><tr><td><div><div><p>MULE-16980</p></div></div></td><td><div><div><p>Allow maven dependency resolution to always update snapshot dependencies</p></div></div></td></tr><tr><td><div><div><p>MULE-16954</p></div></div></td><td><div><div><p>Improve logging infrastructure performance</p></div></div></td></tr><tr><td><div><div><p>MULE-16937</p></div></div></td><td><div><div><p>SDK should no longer that at least one Content parameter to be primary</p></div></div></td></tr><tr><td><div><div><p>MULE-16928</p></div></div></td><td><div><div><p>Review and improve the change for MULE-16919</p></div></div></td></tr><tr><td><div><div><p>MULE-16909</p></div></div></td><td><div><div><p>Support custom parameters in OAuth Dance</p></div></div></td></tr><tr><td><div><div><p>MULE-16908</p></div></div></td><td><div><div><p>Support Client Credentials grant type in the SDK</p></div></div></td></tr><tr><td><div><div><p>MULE-16881</p></div></div></td><td><div><div><p>migrate app deployment file to 4.1</p></div></div></td></tr><tr><td><div><div><p>MULE-16871</p></div></div></td><td><div><div><p>Test performance improvement of backpressure check before policy execution</p></div></div></td></tr><tr><td><div><div><p>MULE-16861</p></div></div></td><td><div><div><p>Normalize namespace usage in ComponentIdentifier between runtime and DataSense</p></div></div></td></tr><tr><td><div><div><p>MULE-16860</p></div></div></td><td><div><div><p>Decouple DataSense from ComponentModel</p></div></div></td></tr><tr><td><div><div><p>MULE-16851</p></div></div></td><td><div><div><p>Implement CompositeConverter#toString to aid in transformers troubleshooting</p></div></div></td></tr><tr><td><div><div><p>MULE-16843</p></div></div></td><td><div><div><p>Move backpressure check before policy application</p></div></div></td></tr><tr><td><div><div><p>MULE-16838</p></div></div></td><td><div><div><p>until-successful attributes should support expressions</p></div></div></td></tr><tr><td><div><div><p>MULE-16755</p></div></div></td><td><div><div><p>ObjectStore expire: account for inconsistencies that may occur in cluster</p></div></div></td></tr><tr><td><div><div><p>MULE-16684</p></div></div></td><td><div><div><p>Make default processing strategy the same as the one for flows</p></div></div></td></tr><tr><td><div><div><p>MULE-16513</p></div></div></td><td><div><div><p>Perform flow backpressure check before source policies are applied</p></div></div></td></tr><tr><td><div><div><p>MULE-16491</p></div></div></td><td><div><div><p>pattern matching for error types in error handlers' type attribute</p></div></div></td></tr><tr><td><div><div><p>MULE-16215</p></div></div></td><td><div><div><p>Make infrastructure parameters to appear as not require for metadata</p></div></div></td></tr><tr><td><div><div><p>MULE-15645</p></div></div></td><td><div><div><p>Enable flowStack by default. This change can result in more detailed information when an error occurs in a Mule application.</p></div></div></td></tr><tr><td><div><div><p>MULE-15596</p></div></div></td><td><div><div><p>Error Handler: Add support for "when" filtering for a certain "type"</p></div></div></td></tr><tr><td><div><div><p>MULE-982</p></div></div></td><td><div><div><p>Logged error should suggest how to enable flowstack</p></div></div></td></tr><tr><td><div><div><p>EE-6898</p></div></div></td><td><div><div><p>Add a way to configure the hazelcast property MERGE_FIRST_RUN_DELAY_SECONDS</p></div></div></td></tr><tr><td><div><div><p>EE-6873</p></div></div></td><td><div><div><p>Replace slashes with underscores in TableNameNormalizer</p></div></div></td></tr><tr><td><div><div><p>EE-6867</p></div></div></td><td><div><div><p>HazelcastLockProvider should call MapNameNormalizer method to normalize map names</p></div></div></td></tr><tr><td><div><div><p>EE-6864</p></div></div></td><td><div><div><p>Escape table names in PostgresSQL database store query builder strategy</p></div></div></td></tr><tr><td><div><div><p>EE-6760</p></div></div></td><td><div><div><p>Make Bitronix XA connection pool configurable</p></div></div></td></tr><tr><td><div><div><p>AGW-3996</p></div></div></td><td><div><div><p>Operation policies are not applied to requester when it is inside XML Connector</p></div></div></td></tr><tr><td><div><div><p>AGW-3921</p></div></div></td><td><div><div><p>Failing to track an api might cause incomplete initialization.</p></div></div></td></tr><tr><td><div><div><p>AGW-3908</p></div></div></td><td><div><div><p>When an unhandled exception is thrown while deploying a policy, the deployer dies.</p></div></div></td></tr><tr><td><div><div><p>AGW-3816</p></div></div></td><td><div><div><p>Fix Mule OAuth authentication failure when Using Client-ID/Client-Secret of Child BG</p></div></div></td></tr><tr><td><div><div><p>AGW-3739</p></div></div></td><td><div><div><p>API is not getting unblocked by Gatekeeper when stopping and starting it from Runtime Manager.</p></div></div></td></tr><tr><td><div><div><p>AGW-3506</p></div></div></td><td><div><div><p>Analytics only being notified for one app.</p></div></div></td></tr><tr><td><div><div><p>AGW-3375</p></div></div></td><td><div><div><p>MapDB is corrupting and stops loading / storing contracts.</p></div></div></td></tr><tr><td><div><div><p>AGW-3181</p></div></div></td><td><div><div><p>Log indicating client id or secret are not provided is never shown.</p></div></div></td></tr><tr><td><div><div><p>AGW-3162</p></div></div></td><td><div><div><p>Stacktrace logged after redeploying offline policy with multiple api pointcuts.</p></div></div></td></tr><tr><td><div><div><p>AGW-3143</p></div></div></td><td><div><div><p>Fix Class Loader Issues generated by getLoggingClassLoader.</p></div></div></td></tr><tr><td><div><div><p>AGW-3142</p></div></div></td><td><div><div><p>Upgrading policy version is not using new policy jar.</p></div></div></td></tr><tr><td><div><div><p>AGW-3105</p></div></div></td><td><div><div><p>Requester policy hangs when headers in requester expression are null.</p></div></div></td></tr><tr><td><div><div><p>AGW-3004</p></div></div></td><td><div><div><p>Policy which does not need IdentityManagement still has it in config Data.</p></div></div></td></tr><tr><td><div><div><p>AGW-2215</p></div></div></td><td><div><div><p>In a policy, when using requester with url instead of request-config, it explodes.</p></div></div></td></tr><tr><td><div><div><p>AGW-4022</p></div></div></td><td><div><div><p>Remove runtime version from templates of default policies.</p></div></div></td></tr><tr><td><div><div><p>AGW-4008</p></div></div></td><td><div><div><p>Update jackson library to latest 2.10.x version</p></div></div></td></tr><tr><td><div><div><p>AGW-3990</p></div></div></td><td><div><div><p>Must upgrade handlebars library version to 4.5.3</p></div></div></td></tr><tr><td><div><div><p>AGW-3952</p></div></div></td><td><div><div><p>Added ability to ignore API’s base path when matching resource level policies.</p></div></div></td></tr><tr><td><div><div><p>AGW-3877</p></div></div></td><td><div><div><p>Improve performance in policies</p></div></div></td></tr><tr><td><div><div><p>AGW-3840</p></div></div></td><td><div><div><p>Add flow name and application name fields, when sending Analytics info to third party systems.</p></div></div></td></tr><tr><td><div><div><p>AGW-3749</p></div></div></td><td><div><div><p>Analytics engine improvements, data recollection.</p></div></div></td></tr><tr><td><div><div><p>AGW-3711</p></div></div></td><td><div><div><p>Enhance User-Agent sent by Gateway to Anypoint</p></div></div></td></tr><tr><td><div><div><p>AGW-3670</p></div></div></td><td><div><div><p>Enable blocking policies being applied to the requester by using "disablePolicies" annotation.</p></div></div></td></tr><tr><td><div><div><p>AGW-3550</p></div></div></td><td><div><div><p>Change Analytics Returning mechanism when no response is set.</p></div></div></td></tr><tr><td><div><div><p>AGW-2090</p></div></div></td><td><div><div><p>Add 400, 412 and 502 to the backoff status codes</p></div></div></td></tr><tr><td><div><div><p>DataWeave</p></div></div></td><td><div><div><ul><li><p>Fix (SE-15642): Index based descendant selector should work as indexing from descendant selector.</p></li><li><p>Fix: Make error dumper include variables.</p></li><li><p>Fix (DW-133): Reuse instance of java when lazy value expressions.</p></li><li><p>Fix (DW-108): MappingCodeGenerator disregards order of arrow mappings when generating script.</p></li><li><p>Fix (SE-8056): Module is not correctly generated when there are recursive types.</p></li><li><p>Fix (SE-15159): Adding a property for security.</p></li><li><p>Fix (DW-126): Wrong type checking between close object and object with fields.</p></li><li><p>Fix: Wrong type checking when calling mapObject with null.</p></li><li><p>Fix (DW-104): Avoid indexWhere fo boxing and unboxing of char and booleans.</p></li><li><p>Fix (SE-14421): Avoid file leaks on indexed files.</p></li><li><p>Fix (SE-14606): Make fromBase64 and toBase64 not to propagate schema for Backwards compatibility.</p></li><li><p>Fix (DW-102): Substring after and Substring After Last should take into account the length of the text.</p></li><li><p>Fix (SE-14623): Fixing Enum Types in Avro.</p></li><li><p>Fix (DW-98): Selecting same part content of different types multiple times should return same content that is in the multipart.</p></li><li><p>Fix (SE-14561): Add support for union type of any kind in Avro.</p></li><li><p>Fix (SE-12726): Do not call to the get() function of a future.</p></li><li><p>Fix deferred mode leaving streams unclosed.</p></li><li><p>Fix (MDF-359): Make stack growable instead of fixed size to avoid unnecessary memory allocation.</p></li><li><p>Fix (MDF-358): Parsing error with single key value pair object.</p></li><li><p>Fix (MDF-357): Adding support for builder static methods for non interfaces.</p></li><li><p>Fix (SE-14264): If not content type is set then binary should be used.</p></li><li><p>Fix (SE-13571): Equal operator for object was affected by the change empty uri and none namespace should be the same.</p></li><li><p>Fix (SE-13571): Empty namespaces should be taken into account as they may be overriding default namespaces.</p></li><li><p>Fix (MDF-355): Avoid creating java writer settings when it is not necessary.</p></li><li><p>Fix: Improve string append performance.</p></li><li><p>Fix: Type parameters where not correctly instantiated when used inside a lambda.</p></li><li><p>Fix: Type resolution on dynamic return type should take into account a specified type.</p></li><li><p>Fix (MDF-352): Split function should take into account writer properties configuration and inferred mimeType properties.</p></li><li><p>Fix: Reduce object allocation in JSON String escaping also fix key length.</p></li><li><p>Fix: Add support for period coercion to number.</p></li><li><p>Fix: GC overhead issue with SeekableStream and EvaluationContext.</p></li><li><p>Fix (SE-13600): Avoid logging the amount of read bytes on range selector over binary.</p></li><li><p>Fix (SE-13440): Avoid registering InMemory DataSources as Closeables as it is not required.</p></li><li><p>Fix: GroupBy now keeps order and performance improvement on groupBy.</p></li><li><p>Fix: Improve performance of reduce array of objects into a single object.</p></li><li><p>Fix (SE-13334): Lower needs to say that works with Comparable types.</p></li><li><p>Fix (SE-13495): Output writer properties should be taken into account when expected data type is used.</p></li><li><p>Fix (SE-12381): Execute simple script on startup to warmup classloader.</p></li><li><p>Fix (SE-12381): Load DataFormats on startup and also load other modules too.</p></li><li><p>Fix (MDF-338): Add com.mulesoft.dw.directbuffer.disable to disable direct buffer.</p></li><li><p>Fix: Capture groups may return null on conditional groups.</p></li><li><p>Fix: Avoid memory leak when automatic coercion of operations.</p></li><li><p>Fix (SE-12381): Make Core to be loaded at statup time.</p></li><li><p>Fix (SE-13334): Fix documentation of max function.</p></li><li><p>Fix (SE-13172): CSV parser for files bigger than 2G.</p></li><li><p>Fix (SE-13071): DataWeaveTypeEmitter should escape literal strings.</p></li></ul></div></div></td></tr></tbody></table>

This version of Mule runtime is bundled with the Runtime Manager Agent plugin version 2.4.5.

## See Also

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