Spring upgraded from 5.1.6 to 5.3.21.
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
DataWeave:
-
Tree
andValue
function modules are new in this release. -
Support for
xsi:types
and thexsiType
function in the Core function module. -
Support streaming by Excel reader.
API Gateway:
-
General performance improvements and issues fixed.
July 2022
Patch release version: 4.2.2-20220622
This patch update addresses the following issues:
Description | Issue |
---|---|
W-10989650 |
DataWeave 2.2.2 is bundled with the Mule 4.2.2 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.
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 mule-ee-patch-4.2.2-20210915-HF1-OCTOBER.zip
in your customer portal.
For guidance with the patching process, see Apply Patch Updates.
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 |
AGW-4823 |
September 2021
Patch release version: 4.2.2-20210823
For guidance with the patching process, see Apply Patch Updates.
The September update addresses the following issues:
Issue | Description |
---|---|
MULE-19387/SE-20319 |
Fixed an issue that prevented deployment of custom policies using the Java Module. |
MULE-19611 |
Updated dependencies in Mule 4.2.2 |
May 2021
Patch release version: 4.2.2-20210419
For guidance with the patching process, see Apply Patch Updates.
The default for the DataWeave XML reader property 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. To address this change, see Change of Behavior with DataWeave Functionality on May 4, 2021. |
The May update addresses the following issues:
Issue | Description |
---|---|
DW-377 |
DataWeave: Support for XML DTD validation is disabled by default. To enable XML DTD validation, use the |
April 2021
Patch release version: 4.2.2-20210322
For guidance with the patching process, see Apply Patch Updates.
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. To prepare for this change, see Change of Behavior with DataWeave Functionality on May 4, 2021. |
The April update addresses the following issues:
Issue | Description |
---|---|
SE-19858 |
Fixed an issue that caused transactions initiated by Anypoint Connector for Virtual Machine (VM Connector) to time out unexpectedly. |
SE-19257 |
DataWeave: Fixed flat file handling of records with values of variable length. |
SE-19846 |
DataWeave: To fix an |
March 2021
Patch release version: 4.2.2-20210304
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-19515/MULE-19209 |
Fixed an issue that caused a memory leak when using a |
SE-18310/MULE-17747/MULE-19187 |
Fixed a |
SE-16673/EE-7664 |
Resolved a problem using Bitronix TM that caused the application to fail when the database was not reachable. |
SE-19030/EE-7653 |
Fixed a problem that prevented XA MQ connections from committing if the flow used a cache element. |
SE-19397 |
Resolved an issue in the January release that caused batch job executions to freeze. |
SE-18881/EE-7654 |
Fixed a validation issue that prevented setting |
AGW-4650 |
Fixed a problem in which removing a policy with contracts before the contracts were downloaded caused the gatekeeper to remain locked. |
AGW-4551 |
Enhanced |
AGW-4533 |
Fixed a problem in which empty payloads in incoming requests were not correctly reported to Analytics. |
AGW-4619 |
Gatekeeper now waits for contracts to download. |
EE-7680 |
Updated the Runtime Manager agent to version 2.4.15. |
SE-19157 |
DataWeave: Fixed an issue in which the splitter generated the wrong exception and caused Scala serialization issues. |
SE-12726 |
DataWeave: Fixed an issue in which accessing |
SE-15096/MULE-18159/MULE-19185 |
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 Apply Patch Updates.
The February update addresses the following issues:
Issue | Description |
---|---|
MULE-19129/SE-19069 |
Resolved problem where Cloudhub’s scheduler was interminently unavailable. |
MULE-16764/SE-11489 |
Fixed issue where Aggregator result outcome which was not maintaining the correct sequence. |
MULE-19097 |
Modified behavior so that non-blocking completion and error callbacks are executed with the same class loader and MDC as the corresponding operation. |
MULE-19068/SE-18382 |
Fixed an issue that caused intermittent |
MULE-18679 |
Fixed a ConcurrentModificationError on adding an startup listener while deploying an app. |
EE-7610/SE-18524 |
Fixed an issue that caused failures to deserialize file store based stream payload in batch. |
MULE-19140/DW-371 |
DataWeave: Fixed an issue with property handling. |
SE-13423 |
DataWeave: Fix an issue where FlatFile could not write |
SE-14631 |
DataWeave: Fixes NPE and selecting same part content of different types multiple times should return same content that is in the multipart. |
SE-15909 |
Fixed issue where Aggregation complete is skipped in the Aggregator module when using a Scatter-Gather pattern. |
SE-16445 |
Fixed |
SE-17677 |
DataWeave: |
SE-16997/MULE-18675 |
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 Apply Patch Updates.
The January update addresses the following issues:
Issue | Description |
---|---|
MULE-19014 |
Upgraded Bouncy Castle to version 1.67. |
MULE-19026 |
Fixed incorrect reconnection behavior in sources, such as the Anypoint Connector for SFTP (SFTP Connector), which caused the sources to work incorrectly. |
MULE-19011 |
Upgraded Jackson to version 2.11. |
MULE-19006, SE-18378 |
Fixed an issue that produced a |
MULE-18059, SE-14766 |
Fixed an issue that caused flows with the Initial State configured to stopped ( |
MULE-18542 |
Added a mechanism inside Mule to prevent memory from leaking when using the Oracle JDBC driver in Anypoint Connector for Database (Database Connector). |
SE-16276 |
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 |
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). |
MULE-19015 |
Fixed a |
SE-14750, MULE-19019 |
Fixed an issue that added a |
EE-7582 |
Fixed an HTTP service regression in which an unexpected error was thrown on a |
November 2020
Patch release version: 4.2.2-20201020
For guidance with the patching process, see Apply Patch Updates.
The November update addresses the following issues:
Issue | Description |
---|---|
SE-13804/MULE-17877 |
Fixed an issue in which Anypoint Connector for SFTP (SFTP Connector) continued reading files if the flow took a long time to complete. |
SE-16853/MULE-18889 |
Resolved an execution problem that occurred when an application used Groovy with Scripting module version 2.0.0. |
SE-17092/MULE-18777 |
Resolved a problem with Anypoint Connector for AMQP (AMQP Connector) that caused the channel count to increase incorrectly after force-closing connections. |
SE-15000/MULE-18794 |
Fixed an issue in which DataSense was unable to find the WSDL file for APIkit for SOAP Project. |
SE-13647/EE-7072 SE-13838/EE-7164 |
Resolved a |
SE-16596/DW-240 |
Fixed an issue in the DataWeave flat file component in which some |
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.2-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-18742 |
Fixed a race condition that produced a |
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-17725/SE-15590 |
Resolved an issue in which a configuration property value for a key could not be found after restarting the domain. |
MULE-17880/SE-12712 |
Fixed multiple warning log entries that occurred when using a caching strategy. |
AGW-4336 |
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. |
SE-16350 |
Fixed a problem in DataWeave in which the CSV reader skipped lines when using |
SE-13440 |
Fixed an |
SE-17212 |
Resolved a problem in which defining a Client ID Enforcement policy failed with encrypted client credentials. |
MULE-18047/MULE-18634 |
Cursor troubleshooting now includes the component that generated a cursor provider. |
MULE-18687 |
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 Apply Patch Updates.
The September update addresses the following issues:
Issue | Description |
---|---|
MULE-18657/SE-14959 |
Fixed a problem that prevented primary node initialization in Anypoint Connector for Salesforce (Salesforce Connector). |
MULE-18665/SE-16278 |
Fixed the |
MULE-18628/SE-16435 |
Resolved a problem in which applications were unable to retrieve objects from the cache due to serialization issues. |
SE-15067 |
DataWeave now properly handles the |
MULE-18548/SE-14272 |
Fixed an issue in which the Cache scope in a cluster configuration did not effectively monitor the cache in the secondary node. |
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-18604/SE-12900 |
Fixed an issue in which NTLM authentication-dancing failed when performing multiple parallel requests requiring renegotiation. |
MULE-17987 |
Fixed a problem that occurred when logging an error for a component that contains a special character, for example, when using the Cryptography module. |
MULE-16688 |
Fixed a problem that occurred when using a property placeholder on an |
MULE-17659/SE-11610 |
Fixed a problem related to custom configuration properties providers not being able to depend on deployment properties. |
MULE-18390 |
Fixed an |
SE-13440 |
Fixed an |
SE-14220 |
Fixed a |
SE-15894 |
JSON binary values are now encoded into strings consistently across DataWeave versions. |
SE-16167 |
The DataWeave Avro module now correctly converts logical types. |
SE-16539 |
Fixed an error that occurred in DataWeave when parsing JSON with whitespace between array elements. |
SE-16620 |
Resolved an issue in which an AVRO decimal value was incorrectly treated as a string and not a decimal. |
MULE-17659/SE-11610 |
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 Apply Patch Updates.
The August update addresses the following issues:
Issue | Description |
---|---|
MULE-18579 |
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 |
MULE-17862, SE-13617 |
Resolved a problem when using Mule 4 on Windows in which MUnit tests failed postexecution, with the |
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. |
MULE-18286 |
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 |
MULE-17726, SE-13425 |
Fixed an issue in which MUnit 2.2.1 failed to stop an artifact cleanly. |
SE-13426 |
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. |
SE-15892 |
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. |
SE-14409 |
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 |
MULE-16668, SE-15200 |
Optimized invocation of Anypoint Connector for NetSuite by reducing the number of |
MULE-17736/MTS-384, SE-14259 |
Resolved the |
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. |
MULE-18284 |
Resolved a deployment problem that occurred when a policy defined an error handler for an The deployment failed because the |
MULE-18492, SE-16365 |
Fixed a serialization problem with policies using the |
MULE-18196, SE-16894 |
The fix for the SE-15056 issue causes applications that use custom policies to fail when sharing the You can revert the behavior by setting the |
SE-13603 |
Fixed an issue in which an application using more than one |
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 Apply Patch Updates.
The July update addresses the following issues:
Issue | Description |
---|---|
AGW-4199 |
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 |
SE-13383 |
Fixed an issue that occurred while moving corrupted domain object store files to the |
SE-14012 |
Mule 4 no longer fails to stream all of the payload to the client. |
SE-14114 |
Fixed an issue in which the DataWeave stream failed to serialize. |
SE-15056 |
An application no longer fails to deploy if it uses the same custom name space as an applied custom policy. |
SE-15067 |
DataWeave now properly handles the |
SE-15201 |
The redundant |
SE-15249 |
Fixed DataWeave attribute selector not dispatching to the correct implementation. |
SE-15536 |
Fixed an issue in which some combinations of |
SE-15800 |
Fixed an issue that caused blocked threads. |
SE-15834 |
Fixed DataWeave inferred types when the output is undefined storage so that the output is recalculated. |
SE-16095 |
Fixed an |
SE-16119 |
Fixed an issue with backslash-character processing when running Studio on Windows, which caused Test Connection in File Connector to fail when the |
SE-16167 |
Fixed an error on processing Apache AVRO logical types in DataWeave scripts. |
SE-16468 |
Fixed an issue with DataWeave |
June 2020
Patch release version: 4.2.2-20200526
For guidance with the patching process, see Apply Patch Updates.
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 |
---|---|
SE-13047 |
Fixed Mule-application deadlock when submitting parallel requests. |
SE-13364 |
|
SE-11087 |
Resolved a problem with semantic versioning build-metadata when deploying an application. |
SE-15269 |
Fixed an issue where |
SE-14245 |
Fixed an issue where an exception affected class loading, even though the class exists in the dependencies using shared libraries. |
SE-13383 |
Fixed an issue that occurred while moving corrupted domain object store files to the |
SE-13596 |
Proxy no longer experiences outage during redeployment in Runtime Fabric, with 2 replicas and rolling update. |
SE-15201 |
Fixed an issue with a redundant |
SE-15592 |
Fixed an incorrect value when accessing variables' content in complex transformations with loops. |
SE-15362 |
Fixed |
SE-15642 |
Resolved DataWeave regression in the index-based descendant selector, so that it now behaves like version 2.2.1. |
SE-15741 |
Optimized a DataWeave performance issue when resolving a parent with type at the parser level. |
SE-15159 |
DataWeave’s XML module now includes a new property to handle XML DTDs. |
SE-15453 |
DataWeave’s XML module now includes a new property to handle escaping |
SE-9907 |
Usage of |
SE-15970 |
Resolved DataWeave’s |
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-14663 |
Fixed an issue that caused |
SE-14946 |
Fixed the error |
SE-13982 |
Fixed an |
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-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-13634 |
Fixed an issue that affected the Web Service Consumer, causing long WSDL parsing times with multiple levels of nested imports. |
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. |
SE-14421 |
Fixed leak problem when processing large payloads in DataWeave function calls from MEL similar to |
SE-14808 |
Fixed |
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-14606 |
The |
SE-14561 and SE-14625 |
DataWeave fixes for union and enum types in Avro schemas. |
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 |
Initial 4.2.2 Release
Release date: November 15, 2019
The initial release of Mule 4.2.2 includes the following fixes:
Issue | Description |
---|---|
MULE-17692 |
TypedValue throws a NPE when calling .toString() on null value. |
MULE-17689 |
DefaultMetadataCacheManager is not reusing the ObjectStore partition. |
MULE-17686 |
NPE when stream is re-managed after previous managing decorator is collected. |
MULE-17661 |
NPE when trying to retrieve metadata using JMS connector. |
MULE-17588 |
Lazy init: <notifications ..> component was not being initialized. |
MULE-17560 |
DefaultPersistentMetadataCacheManager is created per application context, so the shared OS partitioned fails with concurrency. |
MULE-17541 |
Lazy init: <object class="…" '/> not lazy initialized. |
MULE-17510 |
MetadataOutputDelegate was always setting isDynamic to false for MetadataAttributes. |
MULE-17486 |
System.gc() called multiple times when disposing ClassLoaders. |
MULE-17466 |
Maps should not be required to have getters. |
MULE-17463 |
Improve performance of creating FlowBackPressureException. |
MULE-17461 |
Improve performance of DataType cloning. |
MULE-17451 |
Top-level object stores should be started sooner. |
MULE-17449 |
ManagedCursors allow access to unmanaged provider. |
MULE-17429 |
Workaround for MMP-499 in runtime. |
MULE-17409 |
MetadataCacheIdGenerator for configuration elements is not taking into account parameters and only using DslTagId hash. |
MULE-17401 |
Scheduler source should route emitted message through FlowProcessMediator. |
MULE-17384 |
Extensions Maven plugin not honoring extensions dependencies. |
MULE-17383 |
High CPU usage by VM listeners with persistent queues. |
MULE-17373 |
Final "catch-all" check for error handlers does not account for ANY matcher. |
MULE-17344 |
Connections associated with InputStreams should be released when stream is fully consumed. |
MULE-17341 |
Referenced subflows are not being started after stop-start of the application. |
MULE-17333 |
Missing hashCode method in TypedValueTypeAnnotation. |
MULE-17330 |
Race condition when the same CursorProvider is managed twice. |
MULE-17322 |
ComponentResultJsonSerializer uses TCCL to load by SPI type annotations contributed by extensions-api. |
MULE-17313 |
Transaction began by using TryScope are not switching to IO. |
MULE-17312 |
Upgrade commons-pool2 to 2.6.2. |
MULE-17311 |
Services started by an app plugin retain app classloader after reploy/undeploy. |
MULE-17300 |
DefaultArchiveDeployer#deployPackagedArtifact doesn’t redeploy when receiving a URI. |
MULE-17298 |
Splash screen does not list odd-named patches. |
MULE-17296 |
CursorProvider wrongly marked as a consumable class. |
MULE-17288 |
CacheId for fetching metadata keys should be broader. |
MULE-17277 |
Websockets dropped after 30 seconds idle. |
MULE-17267 |
Race condition on source shutdown and restart on connection exception. |
MULE-17264 |
Reintroduce the event buffering when dispatching to a flow. |
MULE-17246 |
Deadlock when building collection DataTypes. |
MULE-17240 |
MultiMap is losing the order when converting to ImmutableMultiMap. |
MULE-17225 |
Loader constraint violation when trying to deploy application. |
MULE-17223 |
MuleApp with Salesforce connector leaking MuleApplicationClassLoader after an undeploy or hotdeploy. |
MULE-17218 |
Mule SDK is leaking extensions configurations over the time. |
MULE-17182 |
CursorProvider set in variables are not managed. |
MULE-17168 |
Remove soft references for app classloaders to avoid OOM on redeploy. |
MULE-17166 |
Wrong group id for HTTP Connector in BundlePluginDependenciesResolver |
MULE-17112 |
Internal libraries of a plugin are overridden by a sharedLib from an app. |
MULE-17110 |
NTLM authentication with dynamic credentials is successful despite credentials changes |
MULE-17102 |
Composite Converters which contain the same transformer chain not filtered out |
MULE-17096 |
NullPointerException when lazy initializing subflow with async scope |
MULE-17091 |
Object streams not automatically closed if <non-repeatable-iterable> option is selected |
MULE-17081 |
PipelineMessageNotificationListener returns a PipelineMessageNotification with null event when an exception is raised in the Mule flow. |
MULE-17080 |
Upgrade SLF4J to 1.7.26 |
MULE-17077 |
PersistentQueueTransactionContext#poll not honoring timeout |
MULE-17065 |
Scatter gather and Parallel Foreach are not working inside error handler |
MULE-17048 |
Race condition when stopping a flow with an inflight event in an async block |
MULE-17045 |
Connections are not closed when streaming operation fails |
MULE-17025 |
ErrorHandler raising error not working |
MULE-17023 |
Nested Try is rolling back tx created by outer try |
MULE-17019 |
Unauthorize operation does not reset ConnectionProviders |
MULE-16994 |
Use of cache instead of WeakHashMap to avoid infinite loop in DefaultLifecycleInterceptor |
MULE-16979 |
Review choice |
MULE-16974 |
FTP reconnection strategy repeat the "start delay" wait time |
MULE-16920 |
"Cannot process event as 'flow' is stopped" when disposing and reinitializing source |
MULE-16890 |
AdoptJDK shown as un unsupported vendor |
MULE-16889 |
DefaultDomainManager#getDomain should retrieve a compatible version of the required domain |
MULE-16817 |
Pooled connections are not removed from the pool when they should evict. |
MULE-16786 |
Dynamic configurations eviction should consider sources as in-flight operations. |
MULE-16285 |
Interception API: Smart connectors inside scopes are not skipped properly. |
MULE-15991 |
No transformers for Iterator to byte[] or String cause error. |
MULE-10347 |
Generics are not resolved for Map implementations. |
MULE-17281 |
SDK needs to allow operations to obtain the effective retry policy. |
MULE-17257 |
Add more detail to FlowBackpressureException. |
MULE-17185 |
Flowref flatmap removal leads to a notorious throughput decrease in the static-flow-ref-subflow case. |
MULE-17161 |
Allow SDK to specify that certain configs should never be used in an implicit way. |
MULE-17114 |
Add the notImported information from MULE-17112 into the plugins packager. |
MULE-17111 |
Create API to propagate a whole custom event when an error occurs in a Processor. |
MULE-17079 |
Remove flatMap from ProactorStreamProcessingStrategy#proactor. |
MULE-17001 |
Avoid unneeded message creation in source callback. |
MULE-16980 |
Allow Maven dependency resolution to always update snapshot dependencies. |
MULE-16954 |
Improve logging infrastructure performance. |
MULE-16513 |
Perform flow back-pressure check before source policies are applied. |
MULE-16215 |
Make infrastructure parameters to appear as not required for metadata. |
EE-6968 |
Avoid references to application classloader in grizzly/reactor static fields in backtrace. |
EE-6927 |
EE version is loading mule-service-weave and mule-service-weave-ee. |
EE-6889 |
JdbcMapStore#loadAll(keys) should only load keys passed as parameter. |
EE-6871 |
Choice performance degradation for Java use case. |
EE-6866 |
When thread waiting in Hz is interrupted, and InterruptedException is not thrown immediately. |
EE-6860 |
Escape table names in Microsoft SQL database store query builder strategy. |
EE-6857 |
File leak when getting dw file for transformation. |
EE-6852 |
Unlock hazelcast lock in the same thread where it was locked. |
EE-6834 |
HTTP Policy module has no Extension model. |
EE-6830 |
Tracking processors are marked as UNKNOWN instead of OPERATION. |
EE-6377 |
Batch Aggregator does not support a JSON payload. |
EE-6338 |
A project using NetSuite fails with OOM after a few redeployments. |
EE-6898 |
Add a way to configure the hazelcast property MERGE_FIRST_RUN_DELAY_SECONDS. |
EE-6873 |
Replace slashes with underscores in TableNameNormalizer. |
EE-6867 |
HazelcastLockProvider should call MapNameNormalizer method to normalize map names. |
EE-6864 |
Escape table names in PostgresSQL database store query builder strategy. |
AGW-3506 |
Analytics are only notified for only one app. |
AGW-3409 |
Analytics events are set with HTTP status code to zero when a request arrives and the policy is being disposed of. |
AGW-3375 |
Fixes the issue when the local contracts database is corrupted. |
AGW-3074 |
Fixes inconsistent error messages and status codes for Basic Auth LDAP-based policy. |
SE-13232 |
Rate limiting SLA policies taking up huge heap in Mule 4.1.5. |
SE-13091 |
JWT policy high performance issue. |
DataWeave |
|
This version of Mule runtime is bundled with the Runtime Manager Agent plugin version 2.4.3.