Mule Runtime 4.2.2 Release Notes

Initial Release: November 15, 2019

Mule 4.2.2 includes enhancements, changes, known limitations, fixes, and patch releases.

New Features and Enhancements


  • Tree and Value function modules are new in this release.

  • Support for xsi:types and the xsiType function in the Core function module.

  • Support streaming by Excel reader.

API Gateway:

  • General performance improvements and issues fixed.


Not applicable.

Known Limitations and Workarounds

Not applicable.

Upgrade Requirements

Not applicable.

Install Monthly Patch Releases

MuleSoft releases cumulative Mule patches on a regular basis, typically once per month. The patch version specifies a Mule version and a patch identifier. Unlike the Mule upgrade process, which is for upgrades to a new minor version of Mule (version n.x to n.y) or to a new patch version (n.x.y to n.x.z), the cumulative patching process applies the latest bug fixes and security enhancements to a specific patch version of Mule. Installing a patch to the wrong Mule version can lead to instabilities and result in issues that are difficult to debug.


Before applying the patch in a production environment, run your MUnit tests on new versions of Mule to validate the application’s behavior with that version.

The following procedure is for updating a patch version of an existing Mule instance:

  1. Stop your Mule instance.

  2. Extract the content of the ZIP file that contains the cumulative patch.

  3. Before proceeding with the installation, review the extracted README file to understand any version-specific steps for installing the patch.

  4. Back up the original content of the MULE_HOME/lib/patches and MULE_HOME/services directories.

  5. Remove any previous patch files from MULE_HOME/lib/patches.

    Important: Do not remove the patches within the MULE_HOME/lib/patches/mule-artifact-patches directory.

  6. Copy the new mule-ee-distribution-standalone-X.Y.Z-YYYYMMDD-patch.jar into MULE_HOME/lib/patches.

    Retain the following in the MULE_HOME/lib/patches directory:

    • mule-ee-distribution-standalone-4.2.2-patch.jar

    • MULE_HOME/lib/patches/mule-artifact-patches

  7. Starting at step 2 in the README file, complete the version-specific service patching instructions.

  8. Restart the Mule instance to pick up the patch.

For more guidance with the patching process, see the support article, How to apply patches to Mule 4.x.

CloudHub and Anypoint Runtime Fabric follow different patching processes.

October 2021

Patch release version: 4.2.2-20210915

To include updated patching instructions, the patch update for the standalone version of Mule was republished as in your customer portal. For guidance with the patching process, see Install Monthly Patch Releases.

The October update addresses the following issues:

Issue Description

Introduced a new mechanism for collecting API gateway usage statistics, which defaults to enabled.

To opt out, include anypoint.platform.metrics_enabled=false in wrapper.conf or as a parameter when starting Mule.


September 2021

Patch release version: 4.2.2-20210823

For guidance with the patching process, see Install Monthly Patch Releases.

The September update addresses the following issues:

Issue Description


Fixed an issue that prevented deployment of custom policies using the Java Module.


Updated dependencies in Mule 4.2.2

May 2021

Patch release version: 4.2.2-20210419

For guidance with the patching process, see Install Monthly Patch Releases.

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 3.9.5, 4.1.6, and 4.2.2 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 May update addresses the following issues:

Issue Description


DataWeave: Support for XML DTD validation is disabled by default. To enable XML DTD validation, use the com.mulesoft.dw.xml.supportDTD system property or the supportDtd XML reader property.

April 2021

Patch release version: 4.2.2-20210322

For guidance with the patching process, see Install Monthly Patch Releases.

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 update addresses the following issues:

Issue Description


Fixed an issue that caused transactions initiated by Anypoint Connector for Virtual Machine (VM Connector) to time out unexpectedly.


DataWeave: Fixed flat file handling of records with values of variable length.


DataWeave: To fix an OutOfMemory error that occurred when mapping many database records, DataWeave now releases resources on stream close.

March 2021

Patch release version: 4.2.2-20210304

For guidance with the patching process, see Install Monthly Patch Releases.

The March update addresses the following issues:

Issue Description


Resolved an issue that prevented opening a new cursor on a closed stream.


Fixed an issue that caused a memory leak when using a try block.


Fixed a DefaultEventContext memory leak error that occurred when a source failed to send an error response.


Resolved a problem using Bitronix TM that caused the application to fail when the database was not reachable.


Fixed a problem that prevented XA MQ connections from committing if the flow used a cache element.


Resolved an issue in the January release that caused batch job executions to freeze.


Fixed a validation issue that prevented setting preparedStatementCacheSize to 0.


Fixed a problem in which removing a policy with contracts before the contracts were downloaded caused the gatekeeper to remain locked.


Enhanced org.mule.runtime.api.healthcheck.ReadyStatus to provide more information.


Fixed a problem in which empty payloads in incoming requests were not correctly reported to Analytics.


Gatekeeper now waits for contracts to download.


Updated the Runtime Manager agent to version 2.4.15.


DataWeave: Fixed an issue in which the splitter generated the wrong exception and caused Scala serialization issues.


DataWeave: Fixed an issue in which accessing vars in a batch step stopped the instance or job from processing.


Fixed an issue in which plugins declared in the domain couldn’t load classes at the application level.

February 2021

Patch release version: 4.2.2-20210129

For guidance with the patching process, see Install Monthly Patch Releases.

The February update addresses the following issues:

Issue Description


Resolved problem where Cloudhub’s scheduler was interminently unavailable.


Fixed issue where Aggregator result outcome which was not maintaining the correct sequence.


Modified behavior so that non-blocking completion and error callbacks are executed with the same class loader and MDC as the corresponding operation.


Fixed an issue that caused intermittent Cannot open a new cursor on a closed stream errors.


Fixed a ConcurrentModificationError on adding an startup listener while deploying an app.


Fixed an issue that caused failures to deserialize file store based stream payload in batch.


DataWeave: Fixed an issue with property handling.


DataWeave: Fix an issue where FlatFile could not write dw keys as values.


DataWeave: Fixes NPE and selecting same part content of different types multiple times should return same content that is in the multipart.


Fixed issue where Aggregation complete is skipped in the Aggregator module when using a Scatter-Gather pattern.


Fixed ReactorRejectedExecutionException when stopping flow containing until-successful.


DataWeave: BinaryValue read buffer is now configurable with property com.mulesoft.dw.buffersize.


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.

January 2021

Patch release version: 4.2.2-20210105

For guidance with the patching process, see Install Monthly Patch Releases.

The January update addresses the following issues:

Issue Description


Upgraded Bouncy Castle to version 1.67.


Fixed incorrect reconnection behavior in sources, such as the Anypoint Connector for SFTP (SFTP Connector), which caused the sources to work incorrectly.


Upgraded Jackson to version 2.11.

MULE-19006, SE-18378

Fixed an issue that produced a can’t get statistics before initialise() is invoked error during the use of a dynamic expiration configuration in a clustered environment.

MULE-18059, SE-14766

Fixed an issue that caused flows with the Initial State configured to stopped (initialState="stopped") to start automatically after stopping and starting the application from Runtime Manager.


Added a mechanism inside Mule to prevent memory from leaking when using the Oracle JDBC driver in Anypoint Connector for Database (Database Connector).


Fixed an issue in running batch jobs that caused the jobs to get stuck and never finish.

SE-17750, MULE-18694

Fixed an issue that prevented applications from deploying on CloudHub 0.2 vCore workers, which caused a java.lang.StackOverflowError.

SE-11428, MULE-18226

Fixed an issue that prevented the finding and loading of libraries when the domain module used native libraries, such as those required by Anypoint Connector for SAP (SAP Connector).


Fixed a Cannot open a new cursor on a closed stream error that occurred when using a nested foreach with a batch size larger than 1.

SE-14750, MULE-19019

Fixed an issue that added a 'Content-length: 0' header for HTTP methods with undefined body semantics (GET, HEAD, and DELETE).


Fixed an HTTP service regression in which an unexpected error was thrown on a SoapFault.

November 2020

Patch release version: 4.2.2-20201020

For guidance with the patching process, see Install Monthly Patch Releases.

The November update addresses the following issues:

Issue Description


Fixed an issue in which Anypoint Connector for SFTP (SFTP Connector) continued reading files if the flow took a long time to complete.


Resolved an execution problem that occurred when an application used Groovy with Scripting module version 2.0.0.


Resolved a problem with Anypoint Connector for AMQP (AMQP Connector) that caused the channel count to increase incorrectly after force-closing connections.


Fixed an issue in which DataSense was unable to find the WSDL file for APIkit for SOAP Project.



Resolved a java.lang.IllegalStateException: Can’t create new contexts after factory is closed error that occurred after restarting an application.


Fixed an issue in the DataWeave flat file component in which some null values were not transformed to zeroes in hexadecimal.


Added a new system property com.mulesoft.dw.valueSelector.selectsAlwaysFirst to avoid caching selected indexes in DataWeave.


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.


Fixed an issue that occurred after Mule runtime engine restarted, which caused Mule application deployment failures while parsing domain shared resources.

October 2020

Patch release version: 4.2.2-20200921

For guidance with the patching process, see Install Monthly Patch Releases.

The October update addresses the following issues:

Issue Description


Fixed an issue that occurred when an app transformed data using variables.


Fixed a race condition that produced a ConcurrentModificationException error in Log4jContextFactory when canceling a registered callback while disposing an application.


Fixed an error that occurred when deploying the Async scope in a custom policy.


Fixed an issue in which the FTP redelivery policy didn’t work in the debugger.


Resolved an issue in which a configuration property value for a key could not be found after restarting the domain.


Fixed multiple warning log entries that occurred when using a caching strategy.


Resolved a problem in which client ID and client secret expressions were incorrectly processed by the encryption engine when applying the Client ID Enforcement policy with the policy encryption mode set to SENSITIVE_ONLY.


Fixed a problem in DataWeave in which the CSV reader skipped lines when using header=false with bodyStartLineNumber.


Fixed an OutOfMemoryError issue that occurred when using the Batch Aggregator Component.


Resolved a problem in which defining a Client ID Enforcement policy failed with encrypted client credentials.


Cursor troubleshooting now includes the component that generated a cursor provider.


Resolved an issue in which an HTTP request with an invalid OAuth token sometimes hung.

September 2020

Patch release version: 4.2.2-20200824

For guidance with the patching process, see Install Monthly Patch Releases.

The September update addresses the following issues:

Issue Description


Fixed a problem that prevented primary node initialization in Anypoint Connector for Salesforce (Salesforce Connector).


Fixed the RegistryLifecycleCallback logger so that it no longer prints the customer’s security key.


Resolved a problem in which applications were unable to retrieve objects from the cache due to serialization issues.


DataWeave now properly handles the #[ sequence inside a String value in Mule operations, such as Logger.


Fixed an issue in which the Cache scope in a cluster configuration did not effectively monitor the cache in the secondary node.


Fixed a memory leak caused by unclosed cursors when used with Foreach loops.


Resolved a memory leak that could cause OutOfMemory errors, which occurred when the app didn’t explicitly nullify the payload at the end of the Foreach loop.


Fixed an issue in which NTLM authentication-dancing failed when performing multiple parallel requests requiring renegotiation.


Fixed a problem that occurred when logging an error for a component that contains a special character, for example, when using the Cryptography module.


Fixed a problem that occurred when using a property placeholder on an import tag with deployment properties, which prevented placeholders from being replaced.


Fixed a problem related to custom configuration properties providers not being able to depend on deployment properties.


Fixed an OutOfMemoryError: Metaspace issue that occurred when running MUnit tests.


Fixed an OutOfMemoryError issue that occurred when using the Batch Aggregator.


Fixed a NullPointerException error that occurred when using the Flat File format in DataWeave.


JSON binary values are now encoded into strings consistently across DataWeave versions.


The DataWeave Avro module now correctly converts logical types.


Fixed an error that occurred in DataWeave when parsing JSON with whitespace between array elements.


Resolved an issue in which an AVRO decimal value was incorrectly treated as a string and not a decimal.


Fixed a problem in which custom configuration properties providers were unable to depend on deployment properties.

August 2020

Patch release version: 4.2.2-20200727

For guidance with the patching process, see Install Monthly Patch Releases.

The August update addresses the following issues:

Issue Description


Resolved an issue in which when an object store expired, it loaded all deserialized entries into memory, doubling memory consumption.

MULE-18288, SE-16676

Resolved a problem that led to memory leaks from plugins and apps that use the Scala language.

MULE-17814, SE-14021

Fixed an issue in which setting -Dmule.classloading.verbose=true prevented MUnit tests from running due to an endless loop.

MULE-17862, SE-13617

Resolved a problem when using Mule 4 on Windows in which MUnit tests failed postexecution, with the IOException: Unable to delete file error.

MULE-18312, SE-13775

Resolved an issue in which running the MUnit test for an application using APIkit failed to upgrade from 4.1.4 to a later version.


Fixed a problem in which error mappings were not used when running an application with lazy initialization on MUnit.

MULE-16965/MULE-17845, SE-13491

Resolved a MuleRuntimeException error namespace already exists that occurred when running MUnit tests.

MULE-17726, SE-13425

Fixed an issue in which MUnit 2.2.1 failed to stop an artifact cleanly.


Resolved a problem in which an application with more than one test suite failed to run MUnit when triggered by a Maven plugin, but ran MUnit correctly in Anypoint Studio.


Fixed a problem in which MUnit tests failed if the app used Object Store after upgrading from Mule 4.2.2 to a later MUnit and Mule runtime release.

MULE-17863, SE-13533

Resolved an issue in which MUnit tests did not run reliably in a Windows environment when started from the command line or Jenkins due to improper file cleanup.

MULE-16987, SE-12167

Resolved a problem in which MUnit did not execute mocking for a custom REST connector with defined attributes.


Fixed an issue in which MUnit 2.2.1 was unable to mock a custom processor in a Try scope.

MULE-18569, SE-16282

Resolved an issue in which the Anypoint Connector for Kafka returned the java.nio.file.InvalidPathException: Illegal char <:> exception when accessing filesystem configuration files.

MULE-16668, SE-15200

Optimized invocation of Anypoint Connector for NetSuite by reducing the number of getServerTime calls when executing a search operation.

MULE-17736/MTS-384, SE-14259

Resolved the NoClassDefFoundError error that occurred when accessing com/google/common/collect/ImmutableMap while running MUnit tests.

MULE-17417, SE-12341

Fixed an issue in which an application running on-premises and managed with Runtime Manager deleted the object store when redeployed.


Resolved a deployment problem that occurred when a policy defined an error handler for an ErrorType issue (such as OS:KEY_NOT_FOUND or HTTP:TIMEOUT) exposed by an extension, and the application defined the same extension.

The deployment failed because the ErrorType could not be found.

MULE-18492, SE-16365

Fixed a serialization problem with policies using the Rate limit SLA policy.

MULE-18196, SE-16894

The fix for the SE-15056 issue causes applications that use custom policies to fail when sharing the ErrorType repository if the app and policy bundle didn’t include all dependencies.

You can revert the behavior by setting the mule.share.errorTypeRepository system property to true.


Fixed an issue in which an application using more than one salesforce:replay-channel operation failed with status code 429.

SE-13603, SE-10677, SE-16728

Upgraded the Object Store v2 plugin to version 4.0.27.

July 2020

Patch release version: 4.2.2-20200709

For guidance with the patching process, see Install Monthly Patch Releases.

The July update addresses the following issues:

Issue Description


Fixed an error when trying to access Gatekeeper and Analytics policy templates in CloudHub Mule 4.x runtimes.

MULE-18506, SE-16470

Reverted MULE-18370 because it caused a key collision in the ManagedCursorProvider cache management.


Fixed an issue that occurred while moving corrupted domain object store files to the Garbage folder.


Mule 4 no longer fails to stream all of the payload to the client.


Fixed an issue in which the DataWeave stream failed to serialize.


An application no longer fails to deploy if it uses the same custom name space as an applied custom policy.


DataWeave now properly handles the #[ sequence inside a String value in Mule operations, such as Logger.


The redundant char[] value generated by DataWeave modules no longer causes a large memory footprint and OutOfMemoryError error.


Fixed DataWeave attribute selector not dispatching to the correct implementation.


Fixed an issue in which some combinations of flow-ref, Async scope, and Try scope fail, causing messages to stop processing.


Fixed an issue that caused blocked threads.


Fixed DataWeave inferred types when the output is undefined storage so that the output is recalculated.


Fixed an OutOfMemoryError: Metaspace error on applications with multiple concurrent deployments and some redeployments.


Fixed an issue with backslash-character processing when running Studio on Windows, which caused Test Connection in File Connector to fail when the Configuration property was present.


Fixed an error on processing Apache AVRO logical types in DataWeave scripts.


Fixed an issue with DataWeave skipNullOn not behaving properly because the value null was ignored in maps.

June 2020

Patch release version: 4.2.2-20200526

For guidance with the patching process, see Install Monthly Patch Releases.

This patch release consolidates fixes to Mule 4.2.2 since the initial release on November 15, 2019. The fixes extend through June 2020.

Issue Description


Fixed Mule-application deadlock when submitting parallel requests.


<bti:xa-data-source-pool> now works with XA transactions.


Resolved a problem with semantic versioning build-metadata when deploying an application.


Fixed an issue where maxConcurrency was not honored when using a flow reference.


Fixed an issue where an exception affected class loading, even though the class exists in the dependencies using shared libraries.


Fixed an issue that occurred while moving corrupted domain object store files to the Garbage folder.


Proxy no longer experiences outage during redeployment in Runtime Fabric, with 2 replicas and rolling update.


Fixed an issue with a redundant char[] generated by DataWeave modules, which lead to a large memory footprint and OutOfMemoryError.


Fixed an incorrect value when accessing variables' content in complex transformations with loops.


Fixed NullPointerException in DataWeave’s XML module.


Resolved DataWeave regression in the index-based descendant selector, so that it now behaves like version 2.2.1.


Optimized a DataWeave performance issue when resolving a parent with type at the parser level.


DataWeave’s XML module now includes a new property to handle XML DTDs.


DataWeave’s XML module now includes a new property to handle escaping > characters.


Usage of java.util.Timezone now works as expected in DataWeave.


Resolved DataWeave’s diff function, which was inverting the expected versus actual comparison.


Fixed issues in which the Scheduler incorrectly ran twice or didn’t honor the configured cron or fixed-frequency setting on restart.


Fixed an issue that generated HTTP request timeouts in several connectors, including Salesforce Connector and Microsoft Dynamics Connector, which cause disruption in their operation.


Fixed an issue that, under high concurrency, might cause a leak in HTTP requests due to a race condition scenario.


Fixed an issue in the Salesforce connector where it did not automatically refresh the OAuth token, causing expired token errors interrupting execution of transactions with Salesforce.


Fixed an issue that caused StackOverflow errors in applications using the Database connector under heavy load.


Fixed the error Failed to read geo directoryjava.nio.file.NoSuchFileException that appeared after deploying an application.


Fixed an OutOfMemory issue that occurred when Database Connector did not properly release heap memory when the request timed out.


Fixed an issue in which an HTTP Request using NTLM authentication did not send the request payload resulting in a timeout request operation.


Fixed an issue in which an HTTP Request using NTLM authentication did not send the request payload resulting in a timeout request operation.


Fixed an issue that affected the Web Service Consumer, causing long WSDL parsing times with multiple levels of nested imports.


Fixed an issue in which batch records didn’t process when the Persistent queues option was enabled.


Reduced log levels for API Gateway recoverable errors.


Added support for HTTP header injection in Anypoint Connector for HTTP.


Fixed leak problem when processing large payloads in DataWeave function calls from MEL similar to #[dw(…​)] that generate temporary files like /tmp/dw-buffer*.tmp.


Fixed dw::core::Strings::substringAfterLast function not working as expected.


Fixed an issue in which the refresh dance did not execute after the access token expired.


Fixed an issue in which Mule apps did not process more than one message from Anypoint MQ.


The toBase64 and fromBase64 functions now behave the same way as in version 4.2.1.

SE-14561 and SE-14625

DataWeave fixes for union and enum types in Avro schemas.


Fixed an issue where the API gateway was using the Business Group organization ID instead of the Master organization ID for OAuth provider operations.


Fixed a DataWeave OOM error Direct buffer memory in 0.1 worker.

Initial 4.2.2 Release

Release date: November 15, 2019

The initial release of Mule 4.2.2 includes the following fixes:

Issue Description


TypedValue throws a NPE when calling .toString() on null value.


DefaultMetadataCacheManager is not reusing the ObjectStore partition.


NPE when stream is re-managed after previous managing decorator is collected.


NPE when trying to retrieve metadata using JMS connector.


Lazy init: <notifications ..> component was not being initialized.


DefaultPersistentMetadataCacheManager is created per application context, so the shared OS partitioned fails with concurrency.


Lazy init: <object class="…​" '/> not lazy initialized.


MetadataOutputDelegate was always setting isDynamic to false for MetadataAttributes.


System.gc() called multiple times when disposing ClassLoaders.


Maps should not be required to have getters.


Improve performance of creating FlowBackPressureException.


Improve performance of DataType cloning.


Top-level object stores should be started sooner.


ManagedCursors allow access to unmanaged provider.


Workaround for MMP-499 in runtime.


MetadataCacheIdGenerator for configuration elements is not taking into account parameters and only using DslTagId hash.


Scheduler source should route emitted message through FlowProcessMediator.


Extensions Maven plugin not honoring extensions dependencies.


High CPU usage by VM listeners with persistent queues.


Final "catch-all" check for error handlers does not account for ANY matcher.


Connections associated with InputStreams should be released when stream is fully consumed.


Referenced subflows are not being started after stop-start of the application.


Missing hashCode method in TypedValueTypeAnnotation.


Race condition when the same CursorProvider is managed twice.


ComponentResultJsonSerializer uses TCCL to load by SPI type annotations contributed by extensions-api.


Transaction began by using TryScope are not switching to IO.


Upgrade commons-pool2 to 2.6.2.


Services started by an app plugin retain app classloader after reploy/undeploy.


DefaultArchiveDeployer#deployPackagedArtifact doesn’t redeploy when receiving a URI.


Splash screen does not list odd-named patches.


CursorProvider wrongly marked as a consumable class.


CacheId for fetching metadata keys should be broader.


Websockets dropped after 30 seconds idle.


Race condition on source shutdown and restart on connection exception.


Reintroduce the event buffering when dispatching to a flow.


Deadlock when building collection DataTypes.


MultiMap is losing the order when converting to ImmutableMultiMap.


Loader constraint violation when trying to deploy application.


MuleApp with Salesforce connector leaking MuleApplicationClassLoader after an undeploy or hotdeploy.


Mule SDK is leaking extensions configurations over the time.


CursorProvider set in variables are not managed.


Remove soft references for app classloaders to avoid OOM on redeploy.


Wrong group id for HTTP Connector in BundlePluginDependenciesResolver


Internal libraries of a plugin are overridden by a sharedLib from an app.


NTLM authentication with dynamic credentials is successful despite credentials changes


Composite Converters which contain the same transformer chain not filtered out


NullPointerException when lazy initializing subflow with async scope


Object streams not automatically closed if <non-repeatable-iterable> option is selected


PipelineMessageNotificationListener returns a PipelineMessageNotification with null event when an exception is raised in the Mule flow.


Upgrade SLF4J to 1.7.26


PersistentQueueTransactionContext#poll not honoring timeout


Scatter gather and Parallel Foreach are not working inside error handler


Race condition when stopping a flow with an inflight event in an async block


Connections are not closed when streaming operation fails


ErrorHandler raising error not working


Nested Try is rolling back tx created by outer try


Unauthorize operation does not reset ConnectionProviders


Use of cache instead of WeakHashMap to avoid infinite loop in DefaultLifecycleInterceptor


Review choice


FTP reconnection strategy repeat the "start delay" wait time


"Cannot process event as 'flow' is stopped" when disposing and reinitializing source


AdoptJDK shown as un unsupported vendor


DefaultDomainManager#getDomain should retrieve a compatible version of the required domain


Pooled connections are not removed from the pool when they should evict.


Dynamic configurations eviction should consider sources as in-flight operations.


Interception API: Smart connectors inside scopes are not skipped properly.


No transformers for Iterator to byte[] or String cause error.


Generics are not resolved for Map implementations.


SDK needs to allow operations to obtain the effective retry policy.


Add more detail to FlowBackpressureException.


Flowref flatmap removal leads to a notorious throughput decrease in the static-flow-ref-subflow case.


Allow SDK to specify that certain configs should never be used in an implicit way.


Add the notImported information from MULE-17112 into the plugins packager.


Create API to propagate a whole custom event when an error occurs in a Processor.


Remove flatMap from ProactorStreamProcessingStrategy#proactor.


Avoid unneeded message creation in source callback.


Allow Maven dependency resolution to always update snapshot dependencies.


Improve logging infrastructure performance.


Perform flow back-pressure check before source policies are applied.


Make infrastructure parameters to appear as not required for metadata.


Avoid references to application classloader in grizzly/reactor static fields in backtrace.


EE version is loading mule-service-weave and mule-service-weave-ee.


JdbcMapStore#loadAll(keys) should only load keys passed as parameter.


Choice performance degradation for Java use case.


When thread waiting in Hz is interrupted, and InterruptedException is not thrown immediately.


Escape table names in Microsoft SQL database store query builder strategy.


File leak when getting dw file for transformation.


Unlock hazelcast lock in the same thread where it was locked.


HTTP Policy module has no Extension model.


Tracking processors are marked as UNKNOWN instead of OPERATION.


Batch Aggregator does not support a JSON payload.


A project using NetSuite fails with OOM after a few redeployments.


Add a way to configure the hazelcast property MERGE_FIRST_RUN_DELAY_SECONDS.


Replace slashes with underscores in TableNameNormalizer.


HazelcastLockProvider should call MapNameNormalizer method to normalize map names.


Escape table names in PostgresSQL database store query builder strategy.


Analytics are only notified for only one app.


Analytics events are set with HTTP status code to zero when a request arrives and the policy is being disposed of.


Fixes the issue when the local contracts database is corrupted.


Fixes inconsistent error messages and status codes for Basic Auth LDAP-based policy.


Rate limiting SLA policies taking up huge heap in Mule 4.1.5.


JWT policy high performance issue.


  • Fix (SE-12381): Execute simple script on startup to warm up class loader.

  • Fix (SE-12381):Load DataFormats on startup and load other modules.

  • MDF-338: Add com.mulesoft.dw.directbuffer.disable to disable direct buffer.

  • Fix NullPointerException when capture groups don’t match on an optional block.

  • Fix: Avoid memory leak when automatic coercion of operations.

  • Fix (SE-12381) Make Core load at startup time.

  • Fix (SE-13172) Fix the CSV parser for files that are larger than 2G.

  • Fix (SE-13334): Fix documentation of the max function.

  • Fix (SE-13071): DataWeaveTypeEmitter should escape literal strings.

  • Fix: Periods should support seconds and fractions of seconds.

  • Fix: Start using Long instead of Int to capture the size of elements and for index selectors.

  • Provide one runtime API to execute DW scripts. Document APIs. Improve DataWeaveScriptingEngine.

  • Try to make WeaveLang ModuleParser global to all apps.

  • Fix #386: Upgrade Java mail (#448).

  • Fix: Read consecutive backslashes correctly in CSV.

  • Fix issue with Excel reader.

  • Improve performance of documentation parsing.

  • Fix (SE-12787): Add support for xsi:types. This type needs to be semantically interpreted.

  • Fix (SE-12627): Fix issue writer properties with camel case needs to be to lower case

  • Fix (SE-12654): Excel streaming feature

  • Fix #425: Support coercion to generics and wrap in optional.

  • Fix #440: Iterator throwing Stream Already Closed.

  • Fix: Avoid bubbling Java exceptions when using sleep and readUrl.

  • Fix #434: Descendant selector is not taking into account child keys.

  • Fix #435: Fix type equality. typeOf("a") == String should be true.

  • Add: Implementations of Tree and Values module.

  • Fix (SE-12733): Fix importing a Mule connector module from another module.

  • Fix: Support for dynamic names on attributes.

  • Fix (SE-12518): Writer Properties not working in Logger.

  • Fix: Try function should make sure that everything is being executed eagerly.

  • Fix: Type pattern matcher with union types and Any.

  • Fix #433: Fix type inference for type pattern matching.

  • Add a system property to identify what closes the stream.

  • Fix #432: Descendant selector was returning non-consumed iterators.

  • Fix (SE-12393): Improve performance on looking for a DataFormat from ID.

  • Fix (SE-12327): Improve performance on divideBy performance. Also increase append performance and prepend performance.

  • Fix (SE-12393): Add system property com.mulesoft.dw.coercionexception.verbose to turn off verbose messages.

  • Fix: Binary data should be written in base64 by the Weave writer

  • Add new DataWeave reader that is more performant.

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

Was this article helpful?

💙 Thanks for your feedback!

Give us your feedback!
We want to build the best documentation experience for you!
Help us improve with your feedback.
Take the survey!