Spring upgraded from 5.1.6 to 5.3.21.
Mule Runtime 4.2.1 Release Notes
Initial release: July 22, 2019
Mule Runtime 4.2.1 includes enhancements, fixes, and patch releases.
July 2022
Patch release version: 4.2.1-20220622
This patch update addresses the following issues:
Description | Issue |
---|---|
W-10989650 |
DataWeave 2.2.1 is bundled with the Mule 4.2.1 release. The July patch release addresses the following DataWeave issues:
Description | Issue |
---|---|
This release fixes Avro property handling. |
W-11324418 |
For guidance with the patching process, see Apply Patch Updates.
March 2021
Patch release version: 4.2.1-20210222
For guidance with the patching process, see Apply Patch Updates.
The March update addresses the following issues:
Issue | Description |
---|---|
SE-19557/MULE-19218 |
Resolved an issue that prevented opening a new cursor on a closed stream. |
SE-18310/MULE-17747/MULE-19187 |
Fixed a |
SE-19397 |
Resolved an issue in the January release that caused batch job executions to freeze. |
EE-7680 |
Updated the Runtime Manager agent to version 2.4.15. |
February 2021
Patch release version: 4.2.1-20210118
For guidance with the patching process, see Apply Patch Updates.
The February update addresses the following issues:
Issue | Description |
---|---|
MULE-18675/SE-16997 |
Fixed an issue where using dynamic configurations for paged or streaming operations, caused a disconnection error when trying to consume the pages or the stream. |
MULE-19129/SE-19069 |
Resolved a problem in which the CloudHub scheduler interrupted intermittently. |
MULE-19068/SE-18382 |
Fixed an issue that caused intermittent |
SE-12654 |
DataWeave: Allowed streaming in Excel format. |
DW-371/MULE-19140 |
DataWeave: Fixed an issue with property handling. |
SE-12393 |
DataWeave: Improved the performance of data format lookup and the |
SE-13423 |
DataWeave: Fixed issue where FlatFile could not write |
SE-14421 |
DataWeave: Fixed issue to avoid file leaks on indexed files. |
SE-14631 |
DataWeave: Fixed issue where NPE and selecting same part content of different types multiple times returns the same content as the multipart. |
January 2021
Patch release version: 4.2.1-20201130
For guidance with the patching process, see Apply Patch Updates.
The January update addresses the following issues:
Issue | Description |
---|---|
SE-11610 |
Fixed an issue in which global properties took precedence over the use of deployment properties. This issue occurred when a custom configuration properties provider was used. |
EE-7443, SE-16276 |
Fixed an issue in running batch jobs that caused the jobs to get stuck and never finish. |
SE-13052 |
Fixed a DataWeave failure to read (transform) several consecutive escaped backslashes in CSV. |
SE-12627 |
Fixed camel-case DataWeave writer properties, which must be handled in lowercase. |
SE-12733 |
Resolved an issue with importing a Mule connector module from another module that was not working in DataWeave. |
SE-12518 |
Fixed DataWeave writer properties that were not working in the Logger component. |
SE-17773 |
Added a new system property |
MULE-19015 |
Fixed a |
November 2020
Patch release version: 4.2.1-20201020
For guidance with the patching process, see Apply Patch Updates.
The November update addresses the following issues:
Issue | Description |
---|---|
SE-13782/MULE-17469 |
Resolved an issue with high memory consumption caused by excessive references to the |
SE-16853/MULE-18889 |
Resolved an execution problem that occurred when an application used Groovy with Scripting module version 2.0.0. |
SE-17773 |
Added a new system property |
SE-17445/MULE-18885 |
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. |
SE-13715/MULE-18812 |
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.1-20200921
For guidance with the patching process, see Apply Patch Updates.
The October update addresses the following issues:
Issue | Description |
---|---|
MULE-18573/SE-15592 |
Fixed an issue that occurred when an app transformed data using variables. |
MULE-18657/SE-14959 |
Fixed a problem that prevented primary node initialization in Anypoint Connector for Salesforce (Salesforce Connector). |
MULE-18164/SE-14610 |
Fixed an error that occurred when deploying the Async scope in a custom policy. |
SE-15624 |
Fixed an issue in which the FTP redelivery policy didn’t work in the debugger. |
MULE-18047/MULE-18634 |
Cursor troubleshooting now includes the component that generated a cursor provider. |
MULE-16897 |
Resolved an issue that occurred with cluster primary-node listener activity after agent initialization. |
September 2020
Patch release version: 4.2.1-20200824
For guidance with the patching process, see Apply Patch Updates.
The September update addresses the following issues:
Issue | Description |
---|---|
SE-16867 |
Fixed an issue with DataWeave that caused the following error:
|
MULE-18628/SE-16435 |
Resolved a problem in which applications were unable to retrieve objects from the cache due to serialization issues. |
MULE-18584/SE-16130 |
Fixed a memory leak caused by unclosed cursors when used with Foreach loops. |
SE-16455 |
Resolved a memory leak that could cause |
MULE-18579/SE-16764 |
Resolved an issue in which when an object store expired, it loaded all deserialized entries into memory, doubling memory consumption. |
MULE-18604/SE-12900 |
Fixed an issue in which NTLM authentication-dancing failed when performing multiple parallel requests requiring renegotiation. |
MULE-18390 |
Fixed an |
August 2020
Patch release version: 4.2.1-20200727
For guidance with the patching process, see Apply Patch Updates.
The August update addresses the following issues:
Issue | Description |
---|---|
MULE-17096 |
Fixed a |
MULE-16987, SE-12167 |
Resolved a problem in which MUnit did not execute mocking for a custom REST connector with defined attributes. |
SE-12193 |
Fixed a problem in which a Mule application containing APIkit for SOAP and an Async scope did not start when launched from Runtime Manager. |
SE-12434 |
Fixed an issue in which an application could not be undeployed on Windows if the anchor file ( |
SE-12743 |
Resolved a problem in which a Cache scope failed validation when the payload was empty when entering the scope. |
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-17862, SE-13617 |
Resolved a problem when using Mule 4 on Windows in which MUnit tests failed postexecution, with the |
SE-13647 |
Fixed a |
MULE-18569, SE-16282 |
Resolved an issue in which the Anypoint Connector for Kafka returned the |
MULE-17341 |
Fixed a problem in which a referenced subflow was not resumed after stopping and starting an application. |
EE-6857 |
Fixed a file leak when retrieving the DataWeave transformation script from a file. |
EE-7072 |
Resolved an issue in which MUnit failed to test an application using batch processing with the |
AGW-3409 |
Fixed an issue that occurred when processing analytics events after policy disposal. |
July 2020
Patch release version: 4.2.1-20200709
For guidance with the patching process, see Apply Patch Updates.
The July update addresses the following issues:
Issue | Description |
---|---|
MULE-18506, SE-16470 |
Reverted MULE-18370 because it caused a key collision in the |
SE-13383 |
Fixed an issue that occurred while moving corrupted domain object store files to the |
SE-14114 |
Fixed an issue in which the DataWeave stream failed to serialize. |
SE-15067 |
DataWeave now properly handles the |
SE-15834 |
Fixed DataWeave inferred types when the output is undefined storage so that the output is recalculated. |
SE-16095 |
Fixed an |
June 2020
Patch release version: 4.2.1-20200518
For guidance with the patching process, see Apply Patch Updates.
This patch release consolidates fixes to Mule 4.2.1 since the initial release on July 22, 2019. The fixes extend through June 2020.
Issue | Description |
---|---|
SE-15592 |
Fixed an incorrect value when accessing variables' content in complex transformations with loops. |
SE-13691 |
Fixed issues in which the Scheduler incorrectly ran twice or didn’t honor the configured cron or fixed-frequency setting on restart. |
SE-15659 |
Fixed an issue that generated HTTP request timeouts in several connectors, including Salesforce Connector and Microsoft Dynamics Connector, which cause disruption in their operation. |
SE-15540 |
Fixed an issue that, under high concurrency, might cause a leak in HTTP requests due to a race condition scenario. |
SE-13371 |
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. |
SE-13634 |
Fixed an issue that affected the Web Service Consumer, causing long WSDL parsing times with multiple levels of nested imports. |
SE-14946 |
Fixed the error |
SE-13547 |
Fixed an issue in which an HTTP Request using NTLM authentication did not send the request payload resulting in a timeout request operation. |
SE-13660 |
Fixed an issue that caused |
SE-13547 |
Fixed an issue in which an HTTP Request using NTLM authentication did not send the request payload resulting in a timeout request operation. |
SE-13300 |
Fixed an issue in which batch records didn’t process when the Persistent queues option was enabled. |
AGW-3949 |
Reduced log levels for API Gateway recoverable errors. |
MULE-17706 |
Added support for HTTP header injection in Anypoint Connector for HTTP. |
MULE-17812 |
Fixed an issue in which the refresh dance did not execute after the access token expired. |
MULE-17812 |
Fixed an issue in which the refresh dance did not execute after the access token expired. |
SE-14595 |
Fixed an issue in which Mule apps did not process more than one message from Anypoint MQ. |
SE-13786 |
Fixed an issue where the API gateway was using the Business Group organization ID instead of the Master organization ID for OAuth provider operations. |
SE-13951 |
Fixed a DataWeave OOM error |
SE-13832 |
Fixed an issue that caused a |
SE-13440 |
Fixed an |
SE-13196 |
Fixed an issue where the configuration property output not correct when the prefix was escaped. |
MULE-16513 |
Flow backpressure check is now performed before source policies are applied. |
SE-13613 |
Fixed a backward-compatibility issue with TLS support. |
SE-13383 |
Fixed an issue that occurred while moving corrupted domain object store files to the |
SE-13677 |
Fixed an issue in which Mule request was not being processed intermittently, even though the request was received by the Listener. |
SE-12836 |
Fixed an issue with the |
SE-13213 |
Fixed error |
SE-13099 |
Added the port where HTTP listens to logs. |
SE-11990 |
Fixed an issue where the |
SE-9292 |
Fixed an issue with filenames in UTF-8 where the £ character in a multipar/form-data was transformed to £ in ASCII. |
SE-13580 |
Fixed an issue that caused a |
SE-13184 |
Fixed an issue where Try Scope with |
SE-13196 |
Fixed an issue with configuration property values that include special characters |
SE-13611 |
Fixed an issue that caused Mule runtime engine to throw exception |
SE-13612 |
Fixed an issue where a CloudHub patch release caused an error:
|
SE-11204 |
Fixed an issue where the HTTP request did not renegotiate NTLM authentication when new credentials were provided. |
EE-6968 |
Fixed a leak in the first classloader that invokes an HTTP service in the Mule app. |
SE-13091 |
Fixed an issue where the JWT policy was not responding under load when the |
SE-13095 |
Inbound metrics did not appear for some apps. |
SE-13004 |
Fixed an issue where the CloudHub worker was unresponsive and unable to start on its own. |
SE-12896 |
Fixed an issue with excessive logging filling |
SE-13388 |
Fixed 100% CPU usage issue due to HTS service. |
SE-13118 |
Fixed inconsistent property loading. |
SE-12626 |
SFTP connector was not reconnecting after |
SE-11329 |
SFTP with public key authentication fails after 5 minutes. |
SE-11198 |
SFTP listener with identity file and start delay set as 0 fails to retrieve file. |
SE-12832 |
Inbound Metrics are missing for app in Anypoint Monitoring. |
SE-11994 |
High CPU - When using VM listener with persistent queue even when the app is idle. |
SE-12772 |
|
SE-12807 |
Cannot open a new cursor on a closed stream inside a |
SE-12279 |
SFTP connection pool is exhausted when file path does not exist. |
SE-10506 |
Out of Memory in Metaspace when redeploying application. |
SE-12204 |
Spring dependency collision between runtime and connectors. |
SE-12583 |
Flow Backpressure error when running DataWeave transformation. |
SE-12495 |
Extensions configuration being leaked over time. |
SE-12028 |
OAuth Module for HTTP Requester is leaking threads. |
SE-12397 |
Unlabelled endpoint is shown within the Monitoring dashboard. |
SE-12451 |
Fixed issue when using the Batch component and streams that caused a |
Initial 4.2.1 Release
Release date: July 22, 2019
The initial release of Mule 4.2.1 includes known limitations and fixes.
Known Limitations and Workarounds
Issue | Description |
---|---|
MULE-17020 |
When debugging an application, Studio is unable to stop over connectors made with the XML SDK and REST Connect connectors. |
MULE-17018 |
Configurations with an expression that contains XML-encoded characters are not allowed.
For example, |
MULE-17079 |
JWT policy performance issues are under load. |
AGW-3299 |
When the Mule OAuth provider is configured to be used by the Mule OAuth token enforcement policy, and organization or environment credentials are not correctly configured, the deployment of the provider fails with a MuleRuntimeException. |
AGW-3506 |
Analytics is generating events for only one API. |
Fixed Issues
Issue | Description |
---|---|
MULE-17061 |
Optimization to avoid thread switch in PS is broken |
MULE-17051 |
Default Error Handler should be looked up after initialization |
MULE-17050 |
SDK Non Blocking operation and policy is not returning a response under load |
MULE-17007 |
@OutputJsonType does not set metadata type id |
MULE-16995 |
Shared runtime deps in app mess up classloading |
MULE-16991 |
Race condition when invalidating cached connections |
MULE-16986 |
XA Transactions fail to rollback on ConnectionException |
MULE-16983 |
Reconnection should not retry when resource has joined active transaction |
MULE-16982 |
ArrayOutOfBoundException when creating custom scheduler |
MULE-16967 |
Database bulk parameters missing on artifact declaration generated from mule-config |
MULE-16964 |
TryScope with no tx fails within subFlow+async |
MULE-16952 |
Publisher returned by applyWithChildContext not completed when source is completed |
MULE-16936 |
Mule 4 JMS Bridge (ActiveMQ) scenario stops working after a certain time |
MULE-16899 |
ClassCast exception when registry lookup finds no match |
MULE-16897 |
No primary node notification listener set on extension sources with cluster support |
MULE-16896 |
Bound connections not released on TransactionException |
MULE-16894 |
IllegalStateException in Polling Source when cluste node is shutting down |
MULE-16892 |
Error handler being executed twice when flow ref is involved |
MULE-16891 |
flowTrace OoM when using foreach with large collections |
MULE-16878 |
StringToEnum Transformer should have different names for each extensionModel |
MULE-16872 |
Async in a transaction executes in the same thread as the transaction |
MULE-16856 |
Starting a flow should fail when a task is rejected from scheduler. |
MULE-16853 |
ConfigurationProperties does not honor properties hierarchy when having prop resolved with placeholder |
MULE-16847 |
MessageProcessors.processWithChildContext must complete the EventContext |
MULE-16841 |
Password mask regex does not consider dw and non-literal expressions. |
MULE-16836 |
Cannot find snapshot artifact via resource loader when trying to scaffold an API |
MULE-16831 |
Fix XA transactions with bitronix |
MULE-16830 |
Global Properties are taking precedence over Application Properties |
MULE-16824 |
LazyInit should initialize the Mule configuration at part of the component initializations phase |
MULE-16790 |
Global ErrorHandler does not resolve transaction |
MULE-16784 |
MuleClassLoaderLookupPolicy wrongly assumming |
MULE-16775 |
OnErrorPropagate in global error handler is not rollbacking tx |
MULE-16758 |
Multithreaded sources are concurrently reconnected more than once |
MULE-16753 |
A transaction is not available error related to execution on a cpuLight thread |
MULE-16744 |
|
MULE-16730 |
Interception API: Validation all throws NullPointerException |
MULE-16725 |
Fix race condition in flow lifecycle handling |
MULE-16657 |
Metaspace leak when generating dynamic configurations |
MULE-15599 |
Serializing an artifact model constructed from serializing a JSON loses data |
MULE-16833 |
Optimize resolution of payload and attributes default parameters |
MULE-16808 |
Update Apache Ant to at least 1.9.12 in 3.x |
MULE-16713 |
Support application/java payloads in redelivery-policy |
EE-6804 |
Bitronix Proxy hides connectivity exceptions |
EE-6797 |
Bitronix exception when redeploying an app using XA transactions |
EE-6796 |
Dirty Bitronix transaction log |
EE-6780 |
Corrupt patches not applied but logged as applied |
EE-6779 |
BitronixTransactionManager built before QueueManager initialize causes NPE |
EE-6774 |
Memory leak on com.mulesoft.mule.runtime.bti.internal.xa.QueueManagerXaResourceProducer |
EE-6769 |
Possible race condition when registering ConnectionFactory in Bitronix |
EE-6710 |
Batch RecordFilteringStrategy is not filtering correctly |
EE-6773 |
Leak of QueueSessionResourceHolder’s: Add troubleshooting information |
EE-6736 |
Update hazelcast to at least 3.12.x in 4.x |
EE-6704 |
Add System Property to set some bitronix logs to debug |
EE-6374 |
Sending large bodies causes OOM error in HTTP requester |
AGW-3213 |
Fix UriBuilder causing class not found |
AGW-3181 |
Log indicating client id or secret are not provided is never shown |
AGW-3142 |
Upgrading policy version is not using new policy jar |
SE-12023 |
Custom policy is not removing its resources as expected |
SE-11918 |
Autodiscovery blocking Gatekeeper from unlocking the API |
SE-11887 |
Using cxf-bundle-minimal or rs-api-2.0.jar in mule application fails the API pairing on CloudHub |
SE-11482 |
Spinoff from SE-10969, JdbcMapStore Object Store in Mule 4.1.5 runtime Cluster environment causes ClassCastException and prevents on-prem Mule Application from pairing with API Manager |
SE-11239 |
AuthenticationServer is leaking objects |
DataWeave |
|
MULE-17060 |
Use the default ProcessingStrategy for policies instead of a custom one |
MULE-16990 |
Improve troubleshooting logging for XA transaction |
MULE-16937 |
SDK should no longer that at least one Content parameter to be primary |
MULE-16909 |
Support custom parameters in OAuth Dance |
MULE-16908 |
Support Client Credentials gran type in the SDK |
MULE-16881 |
Migrate app deployment file to 4.1 |
MULE-16851 |
Implement CompositeConverter#toString to aid in transformers troubleshooting |
MULE-16755 |
ObjectStore expire: account for inconsistencies that may occur in cluster |
MULE-16437 |
Improve ExtensionClient performance |
EE-6760 |
Make Bitronix XA connection pool configurable |
This version of Mule runtime is bundled with the Runtime Manager Agent plugin version 2.3.0.