Anypoint Runtime Fabric Patch Update Release Notes

These release notes describe monthly date-patch updates to the Mule runtime engine on Runtime Fabric. In addition to these release notes, see the Anypoint Runtime Fabric release notes and the complete Anypoint Runtime Fabric documentation.

The following table shows the current schedule for monthly updates. These dates are subject to change.\

Updates are packaged as <major version>-<runtime patch package version>-<image build number>

Month Release Available

October

October 5

September

September 8

August

August 3

July

July 6

June

June 8

May

May 4

April

April 7

March

March 10

The security fix SE-21834, from the August 3 patch release, disables TLS v1 and TLS v1.1 by default. When you deploy an application to Runtime Fabric, you can enable TLS v1 or TLS v1.1 using the following JVM args:

  • Enable TLS v1.0 and TLS v1.1: -Drtf.allow.TLSv1.0+

  • Enable TLS v1.1: -Drtf.allow.TLSv1.1

If you use the Mule Maven Plugin to deploy applications to Runtime Fabric, you must make a PATCH call with the Application Manager API to pass the JVM args, or set them in Runtime Manager.

This change affects all Mule versions for Anypoint Runtime Fabric. Future patches to these releases and future minor releases of Mule will also incorporate this new default.

October 5, 2021

4.4.0-20210915-4

Description Issue

Mule

The tooling service in Anypoint Studio now properly propagates metadata for DataWeave Intersection types.

SE-22333

Mule runtime engine uses the correct version of the disruptor.

SE-19387

Fixed a metaspace memory leak in Anypoint Connector for Database (Database Connector).

SE-15818

HTTP requests with OAuth now use a valid token.

SE-15667

Console logs do not produce repeated log messages for the completion of a single batch job.

SE-11533

Fixed the Illegal reflective access warnings for OpenJDK 11.

SE-13349

After a connection is re-established, SFTP files are now picked up properly.

MULE-18294/SE-13897

In Azure Service Bus Connector, when a flow is stopped, the message listener now stops polling.

SE-17389

API Manager now properly handles connection pool exhaustion and no longer shows APIs in INACTIVE state.

SE-15351

Anypoint Connector for NetSuite (NetSuite Connector) no longer makes excessive getServerTime calls.

SE-15200

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

SE-15056

Applications using Anypoint Connector for Database (Database Connector) under heavy load no longer show StackOverflow errors.

SE-14663

Mule no longer produces an exception related to class loading when the class exists as a dependency and is configured as a shared library.

SE-14245

When an encoded slash is sent as the value of a URI parameter, the associated listener is now found.

SE-14046

Mule 4 no longer fails to stream the complete payload to the client.

SE-14012

The ErrorType no longer changes when entering an Error Handler scope.

SE-13673

Proxies no longer experience outages during redeployment in Anypoint Runtime Fabric configured with two replicas and rolling update.

SE-13596

DataWeave

Added the writeDeclaredNamespaces XML writer property to write all declared namespaces in the root element.

DW-16

Added the writeDeclaration YAML writer property to avoid writing the header declaration.

DW-162

Added a new Strings module for easier string data management.

DW-406

Added the constant folding functionality so that DataWeave replaces operations involving constant values with the actual result. For example, 1024*8 is replaced at compile time with the resulting value 8192.

DW-427

Added flow retyping to the type system, which enables better accuracy within flow-control structures featuring checks that involve typing.

DW-438

Added code inspectors so that quick fixes are suggested with best practices, such as replacing null checks with a default expression, or replacing sizeOf() == 0 with isEmpty().

DW-33/DW-632

Added an inspection to replace using with do blocks.

DW-771

Improved error messages when creating Java objects.

DW-565

Improved performance on floating point number parsing by identifying in advance if the number has a floating point or not.

SE-20614

Extended the common subexpression elimination process to work with index selectors.

SE-19934

Added functions that work with null values to the Core, Arrays, and String modules.

DW-425

Improved JSON performance by copying bytes from input to output directly during JSON-to-JSON data transformations.

DW-230

Improved YAML support of scalar types, string quotations, custom tags, and comment retention.

DW-687

Added the filterTree function to the Tree module to be able to filter any data structure.

DW-160

Added validations for index tokens in CSV format.

DW-577

Added support for the Java classes OptionalInt, OptionalDouble and OptionalLong.

DW-628

Added support for file:/example/file.txt as a valid URL.

DW-195

Added warning when using the design-time only format application/dw without dataOnly mode.

DW-873

Added experimental run and eval functions to dynamically execute scripts.

DW-170

Added the concept of optional function parameters in the type system.

DW-874

Improved CSV streaming to avoid unnecessary processing.

DW-876

Improved the mapObject function to avoid unnecessary processing.

DW-535

Improved the flatten function to avoid unnecessary processing.

DW-509

Improved code validation. Now an error returns when a variable is using the same name as an input.

DW-522

Improved the precision of math operations and added a property to retain the previous behavior: com.mulesoft.dw.math.exact_precision.

SE-16452

Improved handling of big XML files to fix potential I/O exceptions.

DW-250

Fixed error locations when scripts feature dynamic string selectors.

DW-875

Fixed a false negative error message when using multiple union types.

DW-297

The write function return types are now consistent with input types.

DW-298

The update operator no longer fails when working with repeated keys and attributes.

DW-306

Processing of XML documents with comments and streaming enabled now works as expected.

DW-307

DataWeave no longer fails to parse a single key-value pair with a conditional and parentheses.

DW-309

The type system now validates overloaded functions as parameters.

DW-316

Parallel processing on ndjson now works as expected.

DW-325

Fixed a materialization and streaming failure.

DW-368

Fixed the behavior of the slice function.

DW-409/DW-410

Fixed the ability to import namespaces from external modules.

DW-414

DataWeave now produces the error Division by Zero when dividing by 0.0 instead of an internal exception.

DW-415

DataWeave now properly validates that do blocks do not contain any reserved word declaration.

DW-416

Running flatten on flatten no longer causes loss of values.

DW-691

The update operator now works when no attribute is defined.

DW-216

Improved handling of binary data to prevent running out of memory when calculating sizes of processed data.

SE-16559

The com.mulesoft.dw.coercionexception.verbose property no longer logs data from coercion exceptions.

SE-15487

Using nested binary functions no longer produces a StackOverflow error.

SE-16092

DataWeave no longer returns UnsupportedOperationException when parsing an invalid script.

DW-294

Fixed a potential IndexOutOfBoundException when using overloaded functions with four parameters.

DW-159

Added support for dumping Flat File and Avro schemas when com.mulesoft.dw.dump_files is enabled.

DW-137

4.3.0-20210915-3

Description Issue

Metadata now resolves correctly for components with multi-level keys.

MULE-19740/SE-22356

When using the #[flow.name] value in a Set Variable component, Mule now correctly recognizes flow.name.

MULE-19732/SE-20384

Applications now continue correctly when a dynamic flow reference resolves to non-existent flow.

MULE-19742/SE-20838

Mule runtime engine no longer stops accepting requests after a No listener error occurs.

MULE-19533/SE-20958/SE-21576

Applications that include the Dynamic Evaluate component in a sub-flow now deploy correctly.

EE-8018/SE-21777

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.

AGW-4823

Runtime Fabric now suppresses messages with a log level of WARNING or below from the mule-agent in application logs.

SE-22803

4.2.2-20210915-3

Description Issue

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.

AGW-4823

Runtime Fabric now suppresses messages with a log level of WARNING or below from the mule-agent in application logs.

SE-22803

3.9.5-20210915-5

Description Issue

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.

AGW-4823

Runtime Fabric now suppresses messages with a log level of WARNING or below from the mule-agent in application logs.

SE-22803

September 8, 2021

4.3.0-20210823-4

Issue Description

MULE-19707/SE-22200

Fixed an issue that caused some applications and connectors to become unresponsive due to a NullPointerException error.

MULE-19620/SE-21555

Applications now properly release resources allocated by the IBM MQ connector when the application stops.

MULE-19699/SE-21576

Fixed a race condition occuring during parallel deployments that caused deployments to fail.

MULE-19684/SE-22043

Fixed a default error handling issue in the error handler.

MULE-19680/SE-22129

Mule now masks sensitive data and secure properties (e.g. master password) in logs and UI.

MULE-19498

SDK: The @Export annotation now works with the Enum type.

MULE-19624/SE-21593

Restarting an on-premises Mule application with flows with initialState=stopped no longer leaks memory.

SE-21685/EE-7995

Fixed error conditions and messages for MUnit tests.

MULE-19562 /SE-21626

Fixed NullPointerException errors on nested VM Transactions.

MULE-19691/SE-21658

Closing the connection now works correctly if a timeout occurs when an empty payload is sent.

MULE-19622/SE-19944

When handling redirect responses, Mule no longer becomes unresponsive.

SE-21417

DataWeave Flatfile: Added the reader and writer property useMissCharAsDefaultForFill for the flat file format. When this property is set to true, DataWeave uses the fill character configured in the missingValues property to trim or pad elements. If useMissCharAsDefaultForFill is set to false, DataWeave uses the space character.

SE-22171

DataWeave: The distinctBy function now works as expected when used with mapObject or filter.

SE-21050

DataWeave: Fixed an issue that showed an internal exception instead of the expected InvalidUrlEncodingException error message.

SE-21887, SE-21885

Fixed security vulnerabilities

SE-20152

Improved performance of the remove and retrieve operations for Object Store v2 in the Object Store Connector.

4.2.2-20210823-3

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

SE-21887, SE-21885

Fixed security vulnerabilities

SE-20152

Improved performance of the remove and retrieve operations for Object Store v2 in the Object Store Connector.

4.2.120210222-13

Issue Description

SE-21887, SE-21885

Fixed security vulnerabilities

SE-20152

Improved performance of the remove and retrieve operations for Object Store v2 in the Object Store Connector.

4.2.0-20210222-12

Issue

Description

SE-21887, SE-21885

Fixed security vulnerabilities

SE-20152

4.1.6-20210419-9

Issue Description

SE-21887, SE-21885

Fixed security vulnerabilities

SE-20152

Improved performance of the remove and retrieve operations for Object Store v2 in the Object Store Connector.

4.1.5-20210222-11

Issue Description

SE-21887, SE-21885

Fixed security vulnerabilities

SE-20152

Improved performance of the remove and retrieve operations for Object Store v2 in the Object Store Connector.

4.1.4-20210120-12

Issue Description

SE-21887, SE-21885

Fixed security vulnerabilities

SE-20152

Improved performance of the remove and retrieve operations for Object Store v2 in the Object Store Connector.

4.1.3-20210120-12

Issue Description

SE-21887, SE-21885

Fixed security vulnerabilities

SE-20152

Improved performance of the remove and retrieve operations for Object Store v2 in the Object Store Connector.

4.1.2-20210121-14

Issue Description

SE-21887, SE-21885

Fixed security vulnerabilities

SE-20152

Improved performance of the remove and retrieve operations for Object Store v2 in the Object Store Connector.

3.9.5-20210823-3

Issue Description

MULE-19720/SE-22244

WebSphere MQ (WMQ) connector outbound endpoint does not create a transactional context when there is no transaction.

SE-20362/IMC-92

Added a new system property for WebSphere MQ (WMQ) connector to reflect the encryption status of the correlation ID.

SE-21885

Fixed security vulnerabilities

SE-20152

Improved performance of the remove and retrieve operations for Object Store v2 in the Object Store Connector.

3.9.4-20210322-12

Issue Description

SE-21885

Fixed security vulnerabilities

SE-20152

Improved performance of the remove and retrieve operations for Object Store v2 in the Object Store Connector.

3.9.3-20210322-12

Issue Description

SE-21885

Fixed security vulnerabilities

SE-20152

Improved performance of the remove and retrieve operations for Object Store v2 in the Object Store Connector.

3.9.2-20210222-13

Issue Description

SE-21885

Fixed security vulnerabilities

SE-20152

Improved performance of the remove and retrieve operations for Object Store v2 in the Object Store Connector.

3.9.1-20210222-13

Issue Description

SE-21885

Fixed security vulnerabilities

SE-20152

Improved performance of the remove and retrieve operations for Object Store v2 in the Object Store Connector.

3.8.7-20210217-7

Issue Description

SE-21885

Fixed security vulnerabilities

SE-20152

Improved performance of the remove and retrieve operations for Object Store v2 in the Object Store Connector.

August 3, 2021

4.3.0-20210719-2

Issue Description

MULE-19586/SE-21826

Introduces a mule.setVariable.WithNullValue=true property for the Set Variable component, which enables you to create a Mule variable with a null value. In Mule 4.4, this behavior will be the default.

MULE-19485/SE-21019

Incorrect status codes and error descriptions no longer occur when using policies.

EE-7907/SE-20588

Improves the handling of XA transactions when using Anypoint Connector for IBM MQ by fixing the error bitronix.tm.internal.BitronixSystemException - cannot delist an XAResourceHolderState.

EE-7890/SE-20153

Errors from a Batch Aggregator scope are now available within the Batch Step that handles errors.

SE-21198

DataWeave: Introduces a reader property (defaultContentType) and a system property (com.mulesoft.dw.multipart.defaultContentType) to change the default Content-Type for multipart parts.

SE-21632

DataWeave: Temporary files created during the Excel streaming process are now deleted.

SE-21585

DataWeave: Addresses the presence of big objects that are pending finalization.

SE-21873

DataWeave FlatFile: Fixes end-of-input data detection when Copybook structures have multiple segments with repeated composite and element components.

SE-21834

Fixed OS security vulnerabilities. This fix disables TLSv1 and TLSv1.1 by default.

N/A

Made improvements for how properties are injected into the Mule runtime

4.2.2-20210419-7

Issue Description

SE-21834

Fixed OS security vulnerabilities. This fix disables TLSv1 and TLSv1.1 by default.

N/A

Made improvements for how properties are injected into the Mule runtime

4.2.1-20210222-10

Issue Description

SE-21834

Fixed OS security vulnerabilities. This fix disables TLSv1 and TLSv1.1 by default.

N/A

Made improvements for how properties are injected into the Mule runtime

4.2.0-20210222-9

Issue Description

SE-21834

Fixed OS security vulnerabilities. This fix disables TLSv1 and TLSv1.1 by default.

N/A

Made improvements for how properties are injected into the Mule runtime

4.1.6-20210419-6

Issue Description

SE-21834

Fixed OS security vulnerabilities. This fix disables TLSv1 and TLSv1.1 by default.

N/A

Made improvements for how properties are injected into the Mule runtime

4.1.5-20210222-8

Issue Description

SE-21834

Fixed OS security vulnerabilities. This fix disables TLSv1 and TLSv1.1 by default.

N/A

Made improvements for how properties are injected into the Mule runtime

4.1.4-20210120-9

Issue Description

SE-21834

Fixed OS security vulnerabilities. This fix disables TLSv1 and TLSv1.1 by default.

N/A

Made improvements for how properties are injected into the Mule runtime

4.1.3-20210120-9

Issue Description

SE-21834

Fixed OS security vulnerabilities. This fix disables TLSv1 and TLSv1.1 by default.

N/A

Made improvements for how properties are injected into the Mule runtime

4.1.2-20210121-10

Issue Description

SE-21834

Fixed OS security vulnerabilities. This fix disables TLSv1 and TLSv1.1 by default.

N/A

Made improvements for how properties are injected into the Mule runtime

3.9.5-20210719-3

Issue Description

AGW-4869/SE-21462

Custom policies are no longer deleted after restarting an application from Anypoint Runtime Manager.

MULE-19427/SE-19908

A serialization issue no longer occurs after a RoutingException error when using an SFTP transport in a Mule cluster.

SE-21834

Fixed OS security vulnerabilities. This fix disables TLSv1 and TLSv1.1 by default.

N/A

Made improvements for how properties are injected into the Mule runtime

3.9.4-20210322-9

Issue Description

SE-21834

Fixed OS security vulnerabilities. This fix disables TLSv1 and TLSv1.1 by default.

N/A

Made improvements for how properties are injected into the Mule runtime

3.9.3-20210322-9

Issue Description

SE-21834

Fixed OS security vulnerabilities. This fix disables TLSv1 and TLSv1.1 by default.

N/A

Made improvements for how properties are injected into the Mule runtime

3.9.2-20210222-10

Issue Description

SE-21834

Fixed OS security vulnerabilities. This fix disables TLSv1 and TLSv1.1 by default.

N/A

Made improvements for how properties are injected into the Mule runtime

3.9.1-20210222-10

Issue Description

SE-21834

Fixed OS security vulnerabilities. This fix disables TLSv1 and TLSv1.1 by default.

N/A

Made improvements for how properties are injected into the Mule runtime

3.8.7-20210217-5

Issue Description

SE-21834

Fixed OS security vulnerabilities. This fix disables TLSv1 and TLSv1.1 by default.

N/A

Made improvements for how properties are injected into the Mule runtime

July 8, 2021

4.3.0-20210622-6

  • Fixed: Custom metrics from Runtime Fabric are no longer missing in Anypoint Monitoring.

4.2.2-20210419-5

  • Fixed: Custom metrics from Runtime Fabric are no longer missing in Anypoint Monitoring.

4.2.1-20210222-8

  • Fixed: Custom metrics from Runtime Fabric are no longer missing in Anypoint Monitoring.

4.2.0-20210222-6

  • Fixed: Custom metrics from Runtime Fabric are no longer missing in Anypoint Monitoring.

4.1.6-20210419-4

  • Fixed: Custom metrics from Runtime Fabric are no longer missing in Anypoint Monitoring.

4.1.5-20210222-6

  • Fixed: Custom metrics from Runtime Fabric are no longer missing in Anypoint Monitoring.

4.1.4-20210120-7

  • Fixed: Custom metrics from Runtime Fabric are no longer missing in Anypoint Monitoring.

4.1.3-20210120-7

  • Fixed: Custom metrics from Runtime Fabric are no longer missing in Anypoint Monitoring.

4.1.2-20210121-8

  • Fixed: Custom metrics from Runtime Fabric are no longer missing in Anypoint Monitoring.

3.9.5-20210622-6

  • Fixed: Custom metrics from Runtime Fabric are no longer missing in Anypoint Monitoring.

3.9.4-20210322-7

  • Fixed: Custom metrics from Runtime Fabric are no longer missing in Anypoint Monitoring.

3.9.3-20210322-7

  • Fixed: Custom metrics from Runtime Fabric are no longer missing in Anypoint Monitoring.

3.9.2-20210222-7

  • Fixed: Custom metrics from Runtime Fabric are no longer missing in Anypoint Monitoring.

3.9.1-20210222-8

  • Fixed: Custom metrics from Runtime Fabric are no longer missing in Anypoint Monitoring.

3.8.7-20210120-5

  • Fixed: Custom metrics from Runtime Fabric are no longer missing in Anypoint Monitoring.

July 6, 2021

4.3.0-20210622-2

Issue Description

MULE-19226/SE-16379

When deploying policies that use extensions (such as connectors) that are also used in the target application, NoSuchBeanDefinitionException errors are no longer thrown.

MULE-19512/SE-20259

The Anypoint Studio 7.8 debugger no longer stops working unexpectedly when an error occurs in the flow execution.

MULE-19471/SE-20711

The Propagating completion default log level changed from WARN to DEBUG.

MULE-19431

If they are in the same scope or in a nested scope, you can now properly chain transaction interceptors that have different transactionalAction values.

MULE-19290

The initialization policy for pooling profiles now honors the selected option, and no longer initializes to none in all cases.

MULE-19430/SE-20576

Two or more nested XA (Extended Architecture) transactions no longer fail with NullPointerException errors.

MULE-19443/SE-20938

The Set Variable component now creates a variable when the value is null.

SE-20940

The contracts database for API Gateway now self-recovers after experiencing a Wrong index checksum or other errors.

MULE-19418/SE-20254

When the Anypoint Connector for AMQP (AMQP Connector) experiences connectivity errors, transactions are now rolled back, as expected.

SE-19983

DataWeave has improved error reporting for recursive imports.

SE-21133

DataWeave 0x025(LF) byte conversion for IBM037 encoding now works as expected.

SE-20880

DataWeave flat files now contain the property notTruncateDependingOnSubjectNotPresent to avoid truncating the group-item when the subject is not present or the length of the subject of an OCCURS clause is zero. Earlier versions contained this property.

SE-20878

DataWeave no longer raises Negative Index Exception errors when processing JSON files over 10 GB.

MULE-19442

Input stream parameters on a Parameter Group with showInDsl=true now resets after refreshing an expired OAuth token.

MULE-19426/SE-20477

Anypoint MQ connectors are now available in flows after non-transactional MQ publish operations to preserve backwards compatible behavior with Mule 4.2.

SE-20250

Tags and layers behave as expected when setting them through application properties.

N/A

Application metrics are now available from the Anypoint Monitoring Archive API

4.2.2-20210419-2

Issue Description

SE-20250

Tags and layers behave as expected when setting them through application properties.

N/A

Application metrics are now available from the Anypoint Monitoring Archive API

4.2.1-20210222-5

Issue Description

SE-20250

Tags and layers behave as expected when setting them through application properties.

N/A

Application metrics are now available from the Anypoint Monitoring Archive API

4.2.0-20210222-4

Issue Description

SE-20250

Tags and layers behave as expected when setting them through application properties.

N/A

Application metrics are now available from the Anypoint Monitoring Archive API

4.1.6-20210419-2

Issue Description

SE-20250

Tags and layers behave as expected when setting them through application properties.

N/A

Application metrics are now available from the Anypoint Monitoring Archive API

4.1.5-20210222-4

Issue Description

SE-20250

Tags and layers behave as expected when setting them through application properties.

N/A

Application metrics are now available from the Anypoint Monitoring Archive API

4.1.4-20210120-5

Issue Description

SE-20250

Tags and layers behave as expected when setting them through application properties.

N/A

Application metrics are now available from the Anypoint Monitoring Archive API

4.1.3-20210120-5

Issue Description

SE-20250

Tags and layers behave as expected when setting them through application properties.

N/A

Application metrics are now available from the Anypoint Monitoring Archive API

4.1.2-20210121-6

Issue Description

SE-20250

Tags and layers behave as expected when setting them through application properties.

N/A

Application metrics are now available from the Anypoint Monitoring Archive API

3.9.5 20210622-3

Issue Description

SE-20063

The RAML Java parser logger improves log messages.

SE-20800

The soundslike comparison operator now returns false instead of an InvalidExpressionException error.

MULE-19450

The soundslike comparison operator no longer throws InvalidExpressionException error.

SE-20880

DataWeave flat files now contain the property notTruncateDependingOnSubjectNotPresent to avoid truncating the group-item when the subject is not present or the length of the subject of an OCCURS clause is zero. Earlier versions contained this property.

MULE-19284

This release updates XStream to 1.4.16 and Spring Security to 4.2.20.

APIKIT-2943

Upgraded the Java RAML parser to 1.0.44-1.

SE-20250

Tags and layers behave as expected when setting them through application properties.

N/A

Application metrics are now available from the Anypoint Monitoring Archive API

3.9.4-20210322-4

Issue Description

SE-20250

Tags and layers behave as expected when setting them through application properties.

N/A

Application metrics are now available from the Anypoint Monitoring Archive API

3.9.3-20210322-4

Issue Description

SE-20250

Tags and layers behave as expected when setting them through application properties.

N/A

Application metrics are now available from the Anypoint Monitoring Archive API

3.9.2-20210222-5

Issue Description

SE-20250

Tags and layers behave as expected when setting them through application properties.

N/A

Application metrics are now available from the Anypoint Monitoring Archive API

3.9.1-20210222-5

Issue Description

SE-20250

Tags and layers behave as expected when setting them through application properties.

N/A

Application metrics are now available from the Anypoint Monitoring Archive API

3.8.7-20210120-4

Issue Description

SE-20250

Tags and layers behave as expected when setting them through application properties.

N/A

Application metrics are now available from the Anypoint Monitoring Archive API

June 11, 2021

4.3.0 20210609-4

Issue Description

SE-21343

Fixed runtime issue in which API Manager applications did not start up correctly.

June 10, 2021

4.3.0 20210609-2

Issue Description

SE-20497

DataWeave: A StackOverflow error no longer occurs when concatenating arrays.

SE-20846

DataWeave: Applications that use multiple ++ operators no longer fail to deploy.

June 8, 2021

4.3.0 20210601-1

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.

To address this change, see Change of Behavior with DataWeave Functionality on May 4, 2021. (Version 4.3.0 changed behavior in June. Versions 3.9.5, 4.1.6, and 4.2.2 changed in May.)

Issue Description

MULE-19282/SE-17938

Deployments now take into account Maven profiles defined in the pom.xml file, preventing errors due to dependencies not loaded correctly, such as Cannot load class oracle.jdbc.driver.OracleDriver.

MULE-19328/SE-19407

EVENTS_ACCUMULATED error no longer occur after an application restart that caused app’s schedulers to stop working.

MULE-19319

A For Each scope that points to a Flow Reference component using max-concurrency no longer gets stuckt.

MULE-19315/SE-19762

The connector Reconnection Strategy is now correctly honored when running in debugging mode.

MULE-19220/SE-19580

Logging context entries are now propagated correctly to asynchronous SDK operations.

MULE-19297/SE-19166

Streams are no longer closed when consumed inside of a scope.

MULE-19279/SE-15347

Binary payloads are no longer corrupted when using VM queues.

MULE-19289

Logging now includes the original exception when managing reconnection scenarios.

MULE-19291/SE-20299

The timestamp reported by XA Bitronix Transaction is now output correctly.

MULE-19406

The system property name mule..enableStreamingStatistics was corrected to mule.enableStreamingStatistics.

MULE-19342/SE-20247

Scheduler jobs no longer get stuck due to a race condition.

SE-20356

Connection pool now behaves as expected when using a reconnection strategy or using #[] expressions in the connector config element.

MULE-19356/SE-20465

Mule runtime engine no longer shuts down with a NullPointerException error when encountering flows without sources.

MULE-19390/SE-20448

Using a @ParameterGroup annotation with an @ExclusiveOptionals annotation that references another parameter with the same name outside the group no longer causes the deployment to fail with the error the following parameters cannot be set at the same time.

MULE-19408/SE-20491

Error propagation with certain error types when using Mule runtime cluster now works correctly.

MULE-19409

The logs now include JAR files added to the class loader to facilitate troubleshooting server-plugin class loader creation.

MULE-19371/MULE-19370/SE-20386

TieredCompilation no longer prevents apps from working on 0.1 vCore when deployed on a worker with a higher vCore, such as 0.2 vCore.

MULE-19387/SE-20319

Using the Java Module in a policy no longer prevents the policy from deploying successfully.

MULE-19240/SE-20745

Deploying a custom policy on Windows no longer fails if the log file name contains : characters.

MULE-18580

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.

MULE-19347/SE-19450

Anypoint Connector for JMS (Java Message Service) using XA Transactions with Bitronix now honors the reconnection strategy.

MULE-19010

Using the Scatter-Gather component with the Flow Reference component no longer causes MULE:UNKNOWN errors.

SE-20417

The logs now include only one Back Pressure error per exception.

SE-20952

Corrected information in the mule-ee-patch-4.3.0-20210427-MAY-2021.zip README.TXT file.

EE-6454

The Transform Message component now loads resources using the correct encoding.

EE-7739/SE-19692

Undeploying applications in a cluster with FIPS enabled no longer causes the process to hang.

EE-7524

The Cache Scope component no longer creates incompatible cache values during Mule runtime engine upgrades.

EE-7284

Clusters configured to use encrypted communication now work as expected.

AGW-4731

Closed sockets are now recovered correctly when an unexpected platform connection error occurs.

AGW-4747/SE-19546

The client secret of client credentials can now be hashed when storing the credentials in memory and when parsing incoming credentials from a request.

This functionality is disabled by default.

AGW-4797

Removed unused Jersey dependencies.

DW-377

DataWeave: Support for XML DTD validation is now disabled by default.

To enable XML DTD validation, use the com.mulesoft.dw.xml.supportDTD system property or the supportDtd XML reader property.

SE-19933

Schedule-based flows no longer stall after the first batch is processed when the value of maxConcurrency is 1.

SE-20129

DataWeave: The character reader property now correctly handles null as an empty value.

SE-20300

DataWeave: An OutOfMemory error no longer occurs when using MultiPart format.

SE-20372

DataWeave: A StackOverflow error no longer occurs when using StreamCapable check-recursive functions.

SE-16906

Event variables that are visible in a Try scope are now visible inside error handlers.

3.9.5 20210517-2

Issue Description

SE-20983

A class-loading regression, introduced in the May update, that caused a java.lang.ClassNotFoundException: com.ibm.mq.jms.MQConnectionFactory error no longer occurs when using WMQ Connector.

MULE-19374

Updated the Groovy dependency to version 2.4.21.

May 11, 2021

4.3.0 20210322-4

Updated to the container image security patches.

May 4, 2021

4.2.2 20210419-1

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.

Issue Description

DW-377

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.

4.1.6 20210419-1

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.

Issue Description

DW-377

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.

3.9.5 20210419-1

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.

Issue Description

MULE-19327/SE-20359

Provided the system property -Dmule.jms.closeConnectionOnStop=true to enable the forced closure of connections when stopping an application that uses Anypoint Connector for IBM MQ and the WMQ Connector.

MULE-19329/SE-20399

Fixed an issue that caused the DOM of the XML component to not work in Mule runtime engine 3.9.5.

MULE-19296/SE-20229/SE-20376/SE-20492

Fixed an HTTP listener issue that caused all HTTP listeners from applications of a domain to close when redeploying an application from that domain.

MULE-19284/SE-20205

Upgraded the XStream library dependency to 1.4.15.

DW-377

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 7, 2021

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.

4.3.0 20210322-3

Issue Description

N/A

Added support for the persistence gateway service used by the persistent object store. This feature is supported in Runtime Fabric, version 1.9.0 or later.

SE-19725

Fixed an issue that prevents logs from appearing in the console if the logger is configured with a category field.

SE-19374

Added support for default INFO logging to org.mule and com.mulesoft.

SE-17743

Added support for the YEAR timestamp in the application logs.

SE-18317

Fixed an issue where the Gatekeeper health check returned descriptive and non-HTML messages.

SE-20108

Fixed a known issue that could cause a com.esotericsoftware.kryo.KryoException: Buffer underflow error to occur in CloudHub when using Object Store v2 after updating to the March 2021 release.

MULE-19272/SE-18122

Fixed the error Couldn’t find resource: script.dwl neither on classpath or in file system, which occurred when using the Transform Message component (ee:transform) in a subflow called from Parallel For Each (parallel-foreach), Scatter-Gather (scatter-gather), or Cache ee:cache components.

MULE-19262

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.

MULE-19252

Improved the performance of persistent object stores.

MULE-19249/SE-19746

Fixed an issue that caused errors when referencing files on a network share path in a Windows environment.

MULE-19076

Fixed the log message for org.mule.runtime.core.internal.processor.simple.RemoveFlowVariableProcessor.

EE-7703/SE-16631/SE-17432

Fixed an issue that occurred when using XA transactions in the Anypoint Connector for Database (Database Connector).

The application did not resolve metadata correctly and failed when testing with MUnit.

MULE-19242/SE-18799

Fixed a file leak on Windows that prevented Mule from deleting the application’s folder when redeploying, which caused a failure.

SE-19846

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

SE-19257

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

SE-20005

DataWeave: Increased the number of namespaces that can be handled by the XML module to avoid NoSuchElementException errors.

4.2.2 20210322-3

Issue Description

N/A

Added support for the persistence gateway service used by the persistent object store. This feature is supported in Runtime Fabric, version 1.9.0 or later.

SE-19725

Fixed an issue that prevents logs from appearing in the console if the logger is configured with a category field.

SE-19374

Added support for default INFO logging to org.mule and com.mulesoft.

SE-17743

Added support for the YEAR timestamp in the application logs.

SE-18317

Fixed an issue where the Gatekeeper health check returned descriptive and non-HTML messages.

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 OutOfMemory error that occurred when mapping many database records, DataWeave now releases resources on stream close.

4.2.1 20210222-4

Issue Description

N/A

Added support for the persistence gateway service used by the persistent object store. This feature is supported in Runtime Fabric, version 1.9.0 or later.

SE-19725

Fixed an issue that prevents logs from appearing in the console if the logger is configured with a category field.

SE-19374

Added support for default INFO logging to org.mule and com.mulesoft.

SE-17743

Added support for the YEAR timestamp in the application logs.

SE-18317

Fixed an issue where the Gatekeeper health check returned descriptive and non-HTML messages.

4.2.0 20210222-3

Issue Description

SE-19725

Fixed an issue that prevents logs from appearing in the console if the logger is configured with a category field.

SE-19374

Added support for default INFO logging to org.mule and com.mulesoft.

SE-17743

Added support for the YEAR timestamp in the application logs.

SE-18317

Fixed an issue where the Gatekeeper health check returned descriptive and non-HTML messages.

4.1.6 20210322-3

Issue Description

SE-19725

Fixed an issue that prevents logs from appearing in the console if the logger is configured with a category field.

SE-19374

Added support for default INFO logging to org.mule and com.mulesoft.

SE-17743

Added support for the YEAR timestamp in the application logs.

SE-18317

Fixed an issue where the Gatekeeper health check returned descriptive and non-HTML messages.

4.1.5 20210222-3

Issue Description

SE-19725

Fixed an issue that prevents logs from appearing in the console if the logger is configured with a category field.

SE-19374

Added support for default INFO logging to org.mule and com.mulesoft.

SE-17743

Added support for the YEAR timestamp in the application logs.

SE-18317

Fixed an issue where the Gatekeeper health check returned descriptive and non-HTML messages.

4.1.4 20210120-4

Issue Description

SE-19725

Fixed an issue that prevents logs from appearing in the console if the logger is configured with a category field.

SE-19374

Added support for default INFO logging to org.mule and com.mulesoft.

SE-17743

Added support for the YEAR timestamp in the application logs.

SE-18317

Fixed an issue where the Gatekeeper health check returned descriptive and non-HTML messages.

4.1.3 20210120-4

Issue Description

SE-19725

Fixed an issue that prevents logs from appearing in the console if the logger is configured with a category field.

SE-19374

Added support for default INFO logging to org.mule and com.mulesoft.

SE-17743

Added support for the YEAR timestamp in the application logs.

SE-18317

Fixed an issue where the Gatekeeper health check returned descriptive and non-HTML messages.

4.1.2 20210121-5

Issue Description

SE-19725

Fixed an issue that prevents logs from appearing in the console if the logger is configured with a category field.

SE-19374

Added support for default INFO logging to org.mule and com.mulesoft.

SE-17743

Added support for the YEAR timestamp in the application logs.

SE-18317

Fixed an issue where the Gatekeeper health check returned descriptive and non-HTML messages.

3.9.5 20210322-3

Issue Description

SE-19725

Fixed an issue that prevents logs from appearing in the console if the logger is configured with a category field.

SE-19374

Added support for default INFO logging to org.mule and com.mulesoft.

SE-17743

Added support for the YEAR timestamp in the application logs.

SE-18317

Fixed an issue where the Gatekeeper health check returned descriptive and non-HTML messages.

SE-15159

DataWeave: The DataWeave XML module includes a new property to handle XML DTDs.

SE-16329

DataWeave: Fixed an issue in which the lookup function incorrectly called flows asynchronously.

SE-18685

DataWeave: Prevented an error that occurred when reading inboundProperties from an HTTPS endpoint.

SE-19950

DataWeave: Fixed a dependency inconsistency in the Flat File module that caused a java.lang.IncompatibleClassChangeError on certain operating systems.

3.9.4 20210322-3

Issue Description

SE-19725

Fixed an issue that prevents logs from appearing in the console if the logger is configured with a category field.

SE-19374

Added support for default INFO logging to org.mule and com.mulesoft.

SE-17743

Added support for the YEAR timestamp in the application logs.

SE-18317

Fixed an issue where the Gatekeeper health check returned descriptive and non-HTML messages.

SE-10638

DataWeave: Fixed an issue in which high CPU usage during a transformation caused workers to stop processing.

SE-18685

DataWeave: Prevented an error that occurred when reading inboundProperties from an HTTPS endpoint.

SE-19950

DataWeave: Fixed a dependency inconsistency in the flat file module that caused a java.lang.IncompatibleClassChangeError on certain operating systems.

3.9.3 20210322-3

Issue Description

SE-19725

Fixed an issue that prevents logs from appearing in the console if the logger is configured with a category field.

SE-19374

Added support for default INFO logging to org.mule and com.mulesoft.

SE-17743

Added support for the YEAR timestamp in the application logs.

SE-18317

Fixed an issue where the Gatekeeper health check returned descriptive and non-HTML messages.

SE-10638

DataWeave: Fixed an issue in which high CPU usage during a transformation caused workers to stop processing.

SE-14513

DataWeave: Fixed an issue with close streams on lookup.

SE-19950

DataWeave: Fixed a dependency inconsistency in the flat file module that caused a java.lang.IncompatibleClassChangeError on certain operating systems.

3.9.2 20210222-4

Issue Description

SE-19725

Fixed an issue that prevents logs from appearing in the console if the logger is configured with a category field.

SE-19374

Added support for default INFO logging to org.mule and com.mulesoft.

SE-17743

Added support for the YEAR timestamp in the application logs.

SE-18317

Fixed an issue where the Gatekeeper health check returned descriptive and non-HTML messages.

3.9.1 20210222-4

Issue Description

SE-19725

Fixed an issue that prevents logs from appearing in the console if the logger is configured with a category field.

SE-19374

Added support for default INFO logging to org.mule and com.mulesoft.

SE-17743

Added support for the YEAR timestamp in the application logs.

SE-18317

Fixed an issue where the Gatekeeper health check returned descriptive and non-HTML messages.

3.8.7 20210120-3

Issue Description

SE-19725

Fixed an issue that prevents logs from appearing in the console if the logger is configured with a category field.

SE-19374

Added support for default INFO logging to org.mule and com.mulesoft.

SE-17743

Added support for the YEAR timestamp in the application logs.

SE-18317

Fixed an issue where the Gatekeeper health check returned descriptive and non-HTML messages.

March 10, 2021

4.3.0 20210304-1

Issue Description

MULE-19127

Added the ability to redeploy a flow without starting it to enable the server to restart without starting the applications.

AGW-4551

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

AGW-4650

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

AGW-4619

Gatekeeper now waits for contracts to download.

DW-375

DataWeave: Prevented an overflow exception by getting a binary token offset.

SE-11046

Resolved an issue in which MUnit couldn’t run from behind an authenticated a Nexus repository.

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-18881/EE-7654

Fixed a validation issue that prevented setting preparedStatementCacheSize to 0.

SE-19090

DataWeave: Changed local imported modules to be cached to avoid CompilationResult class leaks.

SE-19157

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

SE-19266

DataWeave: Updated to use encoding when converting a string to a byte array.

SE-19442

DataWeave: Fixed an issue in which the pattern matcher didn’t work with comments, causing the script to fail.

MULE-19139

Fixed an issue in which mapped errors threw a MULE:UNKNOWN error, instead of the correct error name.

MULE-18663

When annotating parameters from OAuth-based connection providers with @OAuthParameter and requestAlias, the value of the parameter is now correctly sent when performing the OAuth dance.

MULE-19020

Fixed an issue in which connection errors were not computed in application error-count statistics.

MULE-19143

Fixed an issue that caused a NullPointerException error while using Parallel For Each combined with a For Each under high concurrency.

MULE-19160

Resolved a problem in which retrying policies for operations did not correctly override connection-provider policies.

MULE-19209/SE-19515

Fixed an issue in which a cache held a reference to a thread and a stream, which might cause high memory consumption.

MULE-19219

Fixed an issue in which MediaType did not correctly escape characters.

SE-16747

Resolved an issue that occurred when using the validation:all scope and a validation:is-not-null operation was triggered, the other items in the For Each weren’t processed.

SE-19213

Fixed a NullPointerException error that occurred while processing, under high concurrency, a Parallel For Each with either max-concurrency set to a value other than 1 or not set.

SE-19136

Resolved a problem in which the Add List operation in Anypoint Connector for NetSuite (NetSuite Connector) limited concurrent connections in the Batch Aggregator component.

SE-19515/MULE-19209

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

SE-19294

Resolved an issue in which the application received a rejected from Scheduler exception for HTTP request configurations when processing concurrent requests.

SE-19327

Fixed a SerializationException error that occurred when using the quote reader property (quote="\"") with a batch component.

SE-19557/MULE-19218

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

SE-19606

Fixed a problem in which database connections weren’t returned to the pool or were returned with a delay.

SE-19080/MULE-19157

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).

4.2.2 20210304-1

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 try block.

SE-18310/MULE-17747/MULE-19187

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

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 preparedStatementCacheSize to 0.

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 org.mule.runtime.api.healthcheck.ReadyStatus to provide more information.

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 vars in a batch step stopped the instance or job from processing.

SE-15096/MULE-18159/MULE-19185

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

4.2.1 20210222-1

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 DefaultEventContext memory leak error that occurred when a source failed to send an error response.

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.

4.2.0 20210222-1

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 DefaultEventContext memory leak error that occurred when a source failed to send an error response.

EE-7680

Updated the Runtime Manager agent to version 2.4.15.

4.1.6 20210304-2

Issue Description

MULE-16668/SE-15200

Fixed an issue that caused Anypoint Connector for NetSuite (NetSuite Connector) to make excessive getServerTime calls.

SE-19157

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

SE-19588

DataWeave: Fixed an issue that caused a Scala error when using the keySet function.

SE-12726

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

SE-12923

DataWeave: Fixed a memory issue that occurred when processing large payloads.

SE-14754

DataWeave: Added support for UTF-8 characters in multipart headers to fix an issue that occurred when sending attachments with international characters.

SE-15159

DataWeave: The DataWeave XML module includes a new property to handle XML DTDs.

SE-15960

DataWeave: Upgraded the log4j dependency in the Flat File module.

4.1.5 20210222-1

Issue Description

MULE-16668/SE-15200

Fixed an issue that caused Anypoint Connector for NetSuite (NetSuite Connector) to make excessive getServerTime calls.

SE-19157

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

SE-19588

DataWeave: Fixed an issue that caused a Scala error when using the keySet function.

SE-12726

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

SE-12923

DataWeave: Fixed a memory issue that occurred when processing large payloads.

SE-14754

DataWeave: Added support for UTF-8 characters in multipart headers to fix an issue that occurred when sending attachments with international characters.

SE-15960

DataWeave: Upgraded the log4j dependency in the Flat File module.

3.9.5 20210304-1

Issue Description

SE-19818

DataWeave: Fixed the flow variables lifecycle within transforms, which caused application failure when using the February release.

3.9.4 20210222-2

Issue Description

SE-19818

DataWeave: Fixed the flow variables lifecycle within transforms, which caused application failure when using the February release.

SE-19428

Resolved a cache buffer issue in a dependency library that caused high memory and CPU usage.

3.9.3 20210222-2

Issue Description

SE-19428

Resolved a cache buffer issue in a dependency library that caused high memory and CPU usage.

3.9.2 20210222-2

Issue Description

SE-19428

Resolved a cache buffer issue in a dependency library that caused high memory and CPU usage.

3.9.1 20210222-2

Issue Description

SE-19428

Resolved a cache buffer issue in a dependency library that caused high memory and CPU usage.

February 24, 2021

3.9.5 20210222-2

Issue Description

MULE-19207

Updated the XML Beans dependency to 3.1.0.

MULE-19123

Fixed an issue that caused a CXF proxy response with an empty SOAP:BODY to throw an exception when it was read.

MULE-19096

Updated the Guava dependency to 30.1-android.

MULE-19107

Resolved a NullPointerException caused by the http:header builder.

MULE-19073

Fixed a problem in which an exception in a catch exception strategy did not roll back the transaction.

MULE-19094

Updated the Jetty dependency to 9.4.35.

MULE-19093

Updated the Apache HttpClient (httpclient) dependency to 4.5.13.

MULE-19095

Updated the JUnit dependency to 4.13.1.

MULE-19031

Resolved an issue in which the target parameter of HTTP Request Connector did not work properly with flow variables whose names were escaped by single quotes.

MULE-19089

Fixed problem in which the WMQ outbound endpoint with transacted set in a request-response context stopped processing with no warning.

MULE-19071

Updated the WSS4J dependency to 1.6.19.

MULE-19039

Added back-support behavior in scenarios requiring a correlationId to work as it did until version 3.9.3.

In the earlier behavior, the correlation ID remained the same for messages that were split and aggregated within the application’s flows. The newer behavior adds a sequence suffix to the "split" instances of such messages. The new mule.compoundCorrelationId.disable property has a default value of false. Setting it to true disables the newer mechanism (with the sequence suffix) and uses the previous one in which the correlation ID remains the same.

MULE-19042

Resolved an issue in which the Until Successful scope (until-successful) did not retry on asynchronous events.

MULE-19020

Fixed problem in which connection errors were not computed in the application error count statistics.

MULE-19018

Resolved a problem in which transformers and response transformers were registered in dynamic endpoints when they should not be registered.

MULE-18986

Updated the Bouncycastle dependency to 1.67.

MULE-18981

Updated the jetty-webapp dependency to 9.4.34.v20201102.

MULE-18980

Updated the Jackson dependency to 2.11.

MULE-18982

Updated the jruby-joni dependency to 2.1.40.

MULE-18983

Removed the esapi dependency.

MULE-18869

Updated the opensaml dependency to 2.6.6.

MULE-18887

JMS sessions are now transacted.

MULE-18864

Updated the rhino dependency to 1.7.12.

MULE-18891

Updated the Spring dependency to 4.3.29.

MULE-18866

Updated the Apache Commons Codec dependency to 1.15.

MULE-18862

Updated the Apache Commons IO library dependency to 2.8.

MULE-18868

Updated the Apache Ant dependency to 1.10.9.

MULE-18817

Fixed an issue in which an XML-to-JSON transformation failed when the XML depth exceeded 64.

MULE-18798

Resolved a problem in which the JRuby component failed when assigning variables.

MULE-18799

Fixed serialization issues that caused an out-of-memory (OOM) error when splitting big XML documents in cluster mode.

MULE-18768

Resolved a problem in which cached variables in MEL reported the same error on subsequent transactions.

MULE-17732

Fixed a problem in which the JMS transport was not validating a timeout.

MULE-18754

Resolved an issue in which wire logging was not showing the complete XML in the response.

MULE-18710

Updated the Jetty Server dependency to 9.4.31.v20200723.

MULE-18701

Updated the JRuby dependency to 9.2.14.0.

MULE-18714

Fixed an issue in which it was not possible to resolve the Database connector’s connectionTimeout property.

MULE-17911

Resolved an issue in which the application logged FlowStack : <empty> when LoggerContext.updateLoggers() was called.

MULE-18704

Updated the ognl dependency to 3.0.12.

MULE-18700

Updated the Spring Security dependency to 4.2.18.

MULE-18637

Updated the Dom4J dependency to 2.1.3.

MULE-18681

Fixed a problem in which HTTP Listener Connector returned a chunked transfer-encoded response under HTTP 1.0.

MULE-18582

Resolved a problem in which an application was stuck in "starting" status when SFTP was configured to "reconnect forever" and the connection failed on startup.

MULE-17863

Resolved a file leak in TlsConfiguration.

MULE-18575

Fixed an incorrect mail batch-count verification when using the IMAP transport.

MULE-18548

Resolved an issue in which the in-memory object store did not expired in a secondary node.

MULE-18534

Fixed an issue in which a stored procedure with the CLOB In Out parameter failed to execute on an Oracle database.

MULE-18493

Resolved an issue in which HTTP Connector leaked sockets that were in the CLOSE_WAIT state when the client used HTTP/1.0.

MULE-18481

Fixed an issue with the rollback exception strategy in which redelivery attempts were not honored in the correct way.

MULE-18455

Fixed an issue in which Grizzly returned incorrect error codes with a long header request and a long URI request.

MULE-18503

Resolved a deadlock that occurred when handling a failed deferred response in HTTP.

MULE-18393

Resolved an issue in which the out body was cut under high-load scenarios.

MULE-18461

Fixed an issue in which a payload that was set to a target variable altered the original message MIME type.

MULE-18396

Used the graceful shutdown timeout to allow persistent connections to make a last request.

The corresponding response contains the Connection: close header.

MULE-18380

Added a tolerance time to wait for connections to close upon Mule shutdown.

MULE-18348

Fixed an issue in which MVEL interpreted a Bean property as a Mule variable when using MVEL caching.

MULE-18335

Improved the handling of inflight events and the cleanup of associated resources (such as connections) during shutdown.

MULE-18309

Added a Connection: close header when stopping Mule applications.

This change is needed to produce a graceful shutdown during redeployments.

MULE-18249

Updated the Mule launching script to avoid a readlink error.

MULE-18151

Resolved the closing of all connections (including persistent connections) during Mule shutdown.

This change is needed for redeployments.

MULE-18022

Fixed an issue with IBM MQ and JMS connectors that occurred when a channel was closed and the listener did not recover correctly.

MULE-18006

Resolved a ClassLoader leak that led to application undeployment errors on Windows OS because temporary files could not be properly cleaned up.

MULE-17956

Fixed an issue in which SOAP Kit routed requests to an incorrect path because it was not properly managing override rules.

MULE-17688

Fixed an issue in which Salesforce Connector 'sfdc:oauth-callback' was not properly registered.

MULE-17798

Resolved a problem in which MVEL incorrectly inferred the returnType on a substatement that was surrounded by parentheses.

EE-7212

Fixed an issue in which the Mule runtime engine did not start on macOS Catalina.

EE-7624

Updated the Tanuki wrapper dependency to 3.5.45.

EE-7548

Resolved an issue in which the correlationID was not properly resolved in the WMQ transport when the value of the correlationID was defined through an expression.

EE-7347

Removed FileUtils.deleteFile from the gateway domain script.

AGW-3711

Enhanced the User-Agent sent by API Gateway to improve request tracing by Anypoint Monitoring.

AGW-4013

Resolved exceptions from CORS misconfigurations, which were raised when the application started and stopped.

AGW-4034

Added flow and application names to API Analytics events and exposed generation information about those events.

AGW-4127

SE-15047: Fixed a problem in which an autogenerated proxy was incorrectly propagating headers back to Headers Response at Exception (504).

DW-299

Updated the woodstox dependency to 5.3.0.

AGW-1866

Resolved an issue that caused throttling and rate limiting policies to behave incorrectly when nodes in a Mule cluster were out of sync.

AGW-3038

Enhanced the OAuth Provider to accept a bearer header in lowercase.

AGW-3892

Fixed an issue in which starting and stopping an application broke the throttling and rate limiting policy.

AGW-4226

Resolved a CORS 'Error setting up policy' issue that was caused by a cluster race condition.

AGW-4284

SE-16641: Fixed a high CPU utilization issue with the agw-policy-watcher thread.

AGW-4340

SE-15324: Resolved a duplicated Spring object warning that occurred when applying a throttling policy.

AGW-4400

Resolved an issue with the handling of the Basic Auth Policy response.

MULE-19098

Updated the Jersey dependency to 2.33.

MULE-19070

Updated the xstream dependency to 1.4.15.

MULE-18130

SE-15049: Fixed a problem in which a PKCS12-based keystore with several aliases prevented an application from starting.

SE-15717

Resolved an issue in which the JMS consumer could not reconnect when the session was closed, which disrupted the operation.

MULE-17749

Updated the jcifs dependency to 1.3.19.

DEL-1836

Updated the mule-agent dependency to 1.15.3.

MULE-19125

Updated the Hazelcast dependency to 3.12.11.

EE-7087

Updated the licm dependency to 1.2.4.

MULE-18577

Resolved an issue in which an application failed to redeploy because of a StackOverflow condition.

MULE-18591

Fixed an issue with the NTLM dance renegotiation protocol that was caused by the underlying async libraries.

MULE-18653

Resolved an issue in which it was not possible to undeploy an application that was using an XSLT transformation on Windows.

This issue was caused by dependencies on files that could not be removed.

MULE-19019

Avoided adding the Content-length: 0 header for HTTP methods with undefined body semantics (GET, HEAD, and DELETE).

MULE-19150

Upgraded an underlying library dependency to resolve a java.security.SignatureException: Invalid encoding for signature (java.io.IOException) issue that occurred when using SFTP Connector.

SE-14513

DataWeave: Fixed an issue with close streams on lookup.

SE-14007

DataWeave: Fixed an issue in which OutputStream did not close, causing deferred mode failures for XML.

SE-14927

DataWeave: Fixed an issue with memory management.

SE-14294

DataWeave: Fixed an issue in which variables that can be consumed more than once could not be accessed in more than one script.

SE-15180

DataWeave: Fixed an issue to avoid stack overflow on append inside reduce.

SE-15955

DataWeave: Fixed a problem in which namespaces were not processed correctly when dynamically loading an externalized DataWeave script.

SE-18237

DataWeave: Updated the log4j dependency to version 2.8.2 in the FlatFile module.

SE-10638

DataWeave: Fixed an issue in which high CPU usage during transformation caused workers to stop processing.

SE-18372

DataWeave: Fixed an issue in which a packed decimal was converted incorrectly in the FlatFile module.

SE-18679

DataWeave: Added an option to catch the exception similar to previous behavior.

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

February 2, 2021

4.3.0 20210119-1

Issue Description

MULE-19076

Added warning when the remove variable component tries to remove a non existing variable.

MULE-19038/SE-17832

Fixed a property {app.name} conflict when the application is deployed to CloudHub.

SE-18778

MUnit is unable to dynamic lookup flow references.

MULE-19122/SE-19029

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).

MULE-19129/SE-19069

Resolved a problem in which the CloudHub scheduler got stuck intermittently.

MULE-19118/SE-18583

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.

MULE-18873

Resolved an issue in which routes dropped events during Flow Reference processing in applications that combined Scatter-Gather and Flow Reference components.

MULE-19113/SE-19102

Added logger to BackPressureStrategySelector for better debugging and tracing.

SE-18335

Fixed NullPointerException when using the HTTP Connector inside of a Connector built with XML SDK.

MULE-19097/SE-19126

Fixed issue that cuased CorrelationID to no be consistent throught the Event execution due to unwanted change in the used ClassLoader.

MULE-18159/SE-15096

Fixed an issue where plugins declared in domain could not load classes at application level.

MULE-19088/SE-18749

Fixed an issue that caused a Java.lang.NullPointerException error when trying to run MUnit tests on 4.3.0.

SE-17625

Fixed problem where the error handler component was called multiple times by Until Successful scope incorrectly.

MULE-19068/SE-18382

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

MULE-19049/SE-18521

Resolved incorrect behavior of the First Successful scope that occurred when the scope was within an Error Handler component.

MULE-18679

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

EE-7624

Upgrade Tanuki wrapper to 3.5.45.

SE-18407

Fixed unexpected error The mapper returned a null value. within a Cache scope.

EE-7610/SE-18524

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

AGW-4533

Fixed API reporting for requests with 0 size incoming requests (like GET requests).

DW-325

DataWeave: NDJson was not working when being executed in parallel.

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

SE-13423

DataWeave: Fixed an issue where FlatFile cannot write dw keys as values.

SE-14799

Fixed problem where the onErrorContinue cannot catch a mapped error thrown from a sub flow.

SE-17677

DataWeave: Added feature where the BinaryValue read buffer is now configurable with the property com.mulesoft.dw.buffersize.

SE-18882

DataWeave: Fixed the behavior of the substringBefore() and substringBeforeLast() functions which produced incorrect outputs.

SE-19000

DataWeave: Added a new reader property called tableLimit to control the boundaries of where to read data. Options are: HeaderSize, Unbounded, or the name of the column.

SE-19086

DataWeave: Fixed an issue where stream batching did not work in deferred mode.

SE-19094

DataWeave: Fixed an issue where using for each with batchsize caused the stream to close (StreamClose).

SE-19040

DataWeave: Fixed an issue that caused a NullPointerException when the message of the exception was null.

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.

4.2.2 20210119-1

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 Cannot open a new cursor on a closed stream errors.

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 dw keys as values.

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 ReactorRejectedExecutionException when stopping flow containing until-successful.

SE-17677

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

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.

4.2.1 20210118-1

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 Cannot open a new cursor on a closed stream errors.

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 include property to avoid verbose error messages.

SE-13423

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

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.

4.2.0 20210120-1

Issue Description

MULE-19129/SE-19069

Resolved issue where Cloudhub’s scheduler was disrupted interminently.

MULE-19068/SE-18382

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

MULE-19015/SE-19107

Fixed issue that caused an InputStream to close prematurely when nested for-each processors were redefined with batch-size bigger than 1.

SE-12327

DataWeave: Improved performance for divideBy, append and prepend.

SE-12393

DataWeave: Improved performance of data format lookup and the include property to avoid verbose error messages.

SE-12627

DataWeave: Fixed isssue where camel case writer properties needed to be handled in lower case.

SE-14421

DataWeave: Fixed an issue with leaks on indexed files.

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

4.1.6 20210118-2

Issue Description

MULE-18584/SE-16130

Resolved memory leak while working with a polling use case using the Workday connector.

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

SE-12393

DataWeave: Improved performance of data format lookup and the include property to avoid verbose error messages.

SE-12917

DataWeave: Made string calculation of UnsupportedTypeCoercionException lazy.

SE-13423

DataWeave: Added feature where FlatFile writer can handle dw keys as values.

4.1.5 20210118-2

Issue Description

MULE-16897/SE-11776

Fixed issue where Mule 4 AMQP connector was not switching connections when one of the nodes in cluster went down.

MULE-18584/SE-16130

Resolved memory leak while working with a polling use case using the Workday connector.

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

SE-10844

DataWeave: Fixed an issue where using UTF-8 to load core modules as Crypto::hashWith was not working on Windows.

SE-11527

DataWeave: Added support for dynamic namespaces.

SE-12035

DataWeave: Added support for java.util.Optional as an expected DataType for the expression language.

SE-12917

Dataweave: Made string calculation of UnsupportedTypeCoercionException lazy.

SE-13423

DataWeave: Added feature where FlatFile writer can handle dw keys as values.

4.1.4 20210120-2

Issue Description

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

SE-9379

DataWeave: Fixes an issue that resulted in a FileNotFoundException error when executing an expression in large-batch scenarios. This was caused by prematurely closing the content stream.

SE-11527

DataWeave: Added support for dynamic namespaces.

SE-11246

DataWeave: Fixed an issue to Ccose streams to avoid file leaks.

4.1.3 20210120-1

Issue Description

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

SE-10218

DataWeave: Fixed an issue to avoid duplicating namespaces when using the default namespace.

4.1.2 20210121-1

Issue Description

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

SE-8842

DataWeave: Fixed an issue to prevent the splitting payload expression from modifying the output of other payload expressions.

SE-8944

DataWeave: Fixed an issue where splitting with MIME type / (including parameters) failed.

SE-11246

DataWeave: Fixed a file leak issue in Windows environments.

3.9.4 20210120-4

Issue Description

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

SE-14007

DataWeave: Fixed an issue where OutputStream did not close, causing deferred mode failures for XML.

SE-14294

DataWeave: Fixed an issues where variables that can be consumed more than once could not be accessed in more than one script.

SE-14513

DataWeave: Fixed an issue with close streams on lookup.

SE-15180

DataWeave: Fixed an issue to avoid stack overflow on append inside reduce.

SE-18679

DataWeave: Added an option to catch the exception similar to previous behavior.

SE-18237

DataWeave: Upgrade log4j dependency version to version 2.8.2 in FlatFile module.

3.9.3 20210120-4

Issue Description

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

SE-18237

DataWeave: Upgraded the log4j dependency version to 2.8.2 in the FlatFile module.

3.9.2 20210120-1

Issue Description

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

3.9.1 20210120-4

Issue Description

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

3.8.7 20210120-1

Issue Description

SE-17068

Updated JDK in runtime docker images to include security fixes.

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

January 7, 2021

4.3.0 20210105-1

Issue Description

SE-17068

Updated JDK in runtime docker images to include security fixes.

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-18599

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 showInDsl=true.

MULE-19016

Fixed an issue that could cause a "NullPointerError" when using the Post Message operation of Anypoint Connector for Slack (Slack Connector).

MULE-19006, SE-18378

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

MULE-19002, SE-17479

Fixed an issue in the XML SDK that ignored complex parameters defined as string arrays and with the behavior role.

MULE-18537

Mule now logs reconnection attempts when using the Standard Reconnection Strategy for any connector.

MULE-18929, SE-18107

Fixed an issue in which ActivePolicies set in DefaultPolicyManager 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.

EE-7443, SE-16276

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

SE-16965, AGW-4497

Fixed a metaspace classloader leak that occurred during the redeployment of an application.

SE-16372

Fixed an issue that prevented DataWeave from properly retrieving values when reading CSV files with Byte Order Mark (BOM) and Streaming enabled (streaming=true).

SE-18393

Fixed a DataWeave issue that resulted in a null value when using variables (vars) that were not resolved correctly.

SE-18136

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.

SE-18580

Fixed an issue that caused the Set Variable operation to fail with a MULE:EXPRESSION error when using a DataWeave expression that contained a function definition.

DW-289

Fixed an issue in which upserting an object with update duplicated key-value pairs in some cases.

DW-306

Fixed an issue that prevented the update operator from selecting attributes.

DW-307

Fixed an issue that prevented processing of XML documents when streaming mode was enabled.

MULE-18990

Added an optional warning with information about when an event is dropped.

MULE-19015

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.

MULE-18949

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.

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).

EE-7582

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

4.2.2 20210105-1

Issue Description

SE-17068

Updated JDK in runtime docker images to include security fixes.

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 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.

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 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).

MULE-19015

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).

EE-7582

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

4.2.1 20201130-2

Issue Description

SE-17068

Updated JDK in runtime docker images to include security fixes.

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 com.mulesoft.dw.valueSelector.selectsAlwaysFirst to avoid caching selected indexes in DataWeave.

MULE-19015

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.

4.2.0 20201201-2

Issue Description

SE-17068

Updated JDK in runtime docker images to include security fixes.

SE-16130

Resolved an OutOfMemory issue that occurred because of a failure to release cursors that were managing large XML objects.

EE-7443, SE-16276

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

4.1.6 20201130-2

Issue Description

SE-17068

Updated JDK in runtime docker images to include security fixes.

SE-11410

Fixed the logic for handling control variables that are nested in structures for the FlatFile module.

SE-11650

Fixed the ControlVal property in the Cobol Copybook schema, which was ignored by the FlatFile module.

4.1.5 20201130-2

Issue Description

SE-17068

Updated JDK in runtime docker images to include security fixes.

MULE-18922

Fixed an incompatibility that occurred when migrating to jdk8u265-b01.

MULE-16982, SE-18610

Fixed an issue that raised an ArrayOutOfBoundException exception during the creation of a custom scheduler.

SE-11246

Fixed improperly closed streams to avoid file leaks in DataWeave.

SE-11410

Fixed the logic for handling control variables that are nested in structures for the FlatFile module.

SE-11650

Fixed the ControlVal property in the Cobol Copybook schema, which was ignored in the FlatFile module.

3.9.4 20201030-1

Issue Description

SE-17068

Updated JDK in runtime docker images to include security fixes.

SE-18372

Fixed an issue in which a packed decimal was converted incorrectly in the FlatFile module.

SE-18595

Resolved long delays when throttling policies, which caused the runtime to restart due to Service Level Agreement (SLA) issues.

SE-14656

Fixed an issue in which the Anypoint Connector for WMQ (WMQ Connector) listener stopped processing messages when Anypoint MQ was unavailable.

3.9.3 20201019-5

Issue Description

SE-17068

Updated JDK in runtime docker images to include security fixes.

3.9.2 20201130-1

Issue Description

SE-17068

Updated JDK in runtime docker images to include security fixes.

SE-18515

Fixed a java.lang.ClassNotFoundException on IBM MQ that occurred when using the November 2020 release of the 3.9.2 Mule runtime engine.

SE-10362

Resolved an issue in which the WMQ transport did not reconnect properly when using a synchronous processing strategy.

SE-10743

Fixed a hung thread issue in the WMQ transport when using a synchronous processing strategy.

3.9.1 20201130-1

Issue Description

SE-17068

Updated JDK in runtime docker images to include security fixes.

SE-13596

Fixed an issue in which 'proxies' experienced outages during redeployment in Anypoint Runtime Fabric with 2 replicas and a rolling update.

MULE-18396

Improved the graceful timeout for shutdowns so that persistent connections can make a last request. The corresponding response contains the Connection: close header.

MULE-18335

Fixed an issue that occurred while Mule runtime engine waited for inflight events to close idle connections during the shutdown phase.

MULE-18151

Resolved an issue in which persistent HTTP connections did not close effectively upon a Mule shutdown. This issue prevented proper rolling restarts.

MULE-18380

Added a tolerance time to wait for connections to close during Mule runtime engine’s shutdown phase.

MULE-15004

Fixed an issue that ignored the serverTimeout attribute on tcp:server-socket.

MULE-15062

Fixed an issue that generated a conflict between connectionIdleTimeout and socket timeout. Also fixed an issue in which negative values in connectionIdleTimeout were treated as zero values.

3.8.7 20201210-2

Issue Description

SE-17068

Updated JDK in runtime docker images to include security fixes.

SE-18595

Resolved long delays when throttling policies, which caused the runtime to restart due to Service Level Agreement (SLA) issues.

November 4, 2020

4.3.0 20201021

Issue Description

Improved application network metric tracking.

SE-17806/MULE-18883

Fixed a CloudHub issue in which the Scheduler stopped but reported its status as Running.

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-16989/MULE-18805

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.

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-16853/MULE-18889

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

MULE-18884

Resolved a memory leak that caused Mule runtime engine to crash after multiple redeployments of an app.

SE-15000/MULE-18794

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

SE-16933/MULE-18698

Fixed a regression in which dynamic configurations were not properly disposed, which caused out of memory errors.

SE-17756/MULE-18803

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.

SE-16596/DW-240

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

SE-17773

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

SE-17873

Fixed the following DataWeave error that occurred while converting Instant to LocalDateTime with MIN and MAX:

An exception occurred while trying to access field function java.time.Instant.MIN. Caused by: java.time.DateTimeException: Invalid value for Year

FV-833

Fixed an issue in which joinBy failed to validate against signatures in DataWeave. //correct issue number?

SE-9907

Fixed an issue with DataWeave in which java.util.Timezone provided a ZoneInfo Java class, rather than the time zone ID, such as "America/Los Angeles".

SE-14220

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

SE-15970

Resolved an issue with the DataWeave diff function, which inverted the values of the expected and actual keys.

SE-16350

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

SE-16883

Fixed an issue with the DataWeave Mule::causedBy function, which didn’t have the correct type defined for Error.

SE-17149

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.

SE-17212

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

SE-17392

Fixed an issue in which DataWeave didn’t correctly handle an internal UnsupportedTypeCoercionException error while processing a batch of records.

SE-17446

Resolved an issue in DataWeave in which conversion from Excel to DataWeave didn’t correctly ignore empty lines in Excel.

SE-17520

Fixed a problem in which DataWeave didn’t correctly process keys that use a literal $ string value.

SE-17562

Fixed a problem in which a migrated MUnit test from a previous Mule version executed a mocked connector.

SE-17570

Resolved a DataWeave issue that caused a StackOverflow error when using some and every functions with large arrays.

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.

SE-12712/MULE-17880

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

SE-15592/MULE-18573

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

MULE-18872

Fixed an issue with the runtime logging that could cause out of memory issues.

SE-16439/MULE-18696

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.

SE-16823/MULE-18712

Resolved a problem in which it was not possible to mock scripting:execute processors when running MUnit tests.

SE-17554/MULE-18739

Fixed the default value resolution for the Scheduler component’s disallowConcurrentExecution attribute so that you don’t need to define it explicitly.

MULE-18742

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

4.2.2 20201020

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 java.lang.IllegalStateException: Can’t create new contexts after factory is closed error that occurred after restarting an application.

SE-16596/DW-240

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

SE-17773

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

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.

4.2.1 20201020

Issue Description

SE-13782/MULE-17469

Resolved an issue with high memory consumption caused by excessive references to the org.mule.runtime.config.internal.model.ApplicationModel class.

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 com.mulesoft.dw.valueSelector.selectsAlwaysFirst to avoid caching selected indexes in DataWeave.

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.

4.2.0 20201020

Issue Description

SE-13782/MULE-17469

Resolved an issue with high memory consumption caused by excessive references to the org.mule.runtime.config.internal.model.ApplicationModel class.

MULE-17916

Fixed a MUnit execution error in APIkit for SOAP.

SE-15704/MULE-18375

Fixed an issue in which a custom policy that applied to outbound requests changed the behavior of an API by changing response values.

SE-16853/MULE-18889

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

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.

SE-17812

Fixed a problem that caused the following error:

No qualifying bean of type org.mule.runtime.module.extension.internal.runtime.client.strategy.ExtensionsClientProcessorsStrategyFactory

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.

4.1.6 20201019

Issue Description

SE-13715, MULE-18812

Fixed an issue that occurred after Mule runtime engine restarted. The issue caused Mule application deployment failures while parsing resources that were shared through a domain.

MULE-18922

Fixed incompatibility when migrating to use jdk8u265-b01.

4.1.5 20201019

Issue Description

SE-13782/MULE-17469

Resolved an issue with high memory consumption caused by excessive references to the org.mule.runtime.config.internal.model.ApplicationModel class.

SE-12121/MULE-16994

Fixed an infinite recursion issue that occurred with high throughput, which caused high CPU consumption.

SE-10518/MULE-16314

Removed repeated and unneeded WARN message that referenced the org.mule.runtime.core.internal.util.store.MonitoredObjectStoreWrapper class.

SE-10694/MULE-16435

Resolved a problem with logging configuration in which the logger wrote to the wrong file.

SE-13838/EE-7164

Fixed the Can’t create new contexts after factory is closed error message that occurred after restarting an application.

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.

EE-7268

Fixed a memory leak that occurred when restarting batch applications.

4.1.4 20201019

Issue Description

SE-11428/MULE-18226

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

3.9.4 20201019

Issue Description

SE-15717

Fixed a JMS transport problem that prevented reconnection after the session was closed due to a connection reset.

SE-13533/MULE-17863

Resolved a file leak that occurred when using TLS configurations.

SE-15493

Improved error reporting with FlowStack exceptions when error trace logs are missing context.

3.9.3 20201019

Issue Description

SE-15717

Fixed a JMS transport problem that prevented reconnection after the session was closed due to a connection reset.

SE-13533/MULE-17863

Resolved a file leak that occurred when using TLS configurations.

3.9.2 20201019

Issue Description

SE-15717

Fixed a JMS transport problem that prevented reconnection after the session was closed due to a connection reset.

SE-13533/MULE-17863

Resolved a file leak that occurred when using TLS configurations.

3.9.1 20201019

Issue Description

SE-17557/MULE-18768

Fixed a Mule Expression Language (MEL) issue in which variables were cached, resulting in the same error being sent in following transaction executions.

SE-13533/MULE-17863

Resolved a file leak that occurred when using TLS configurations.

October 6, 2020

4.2.2 v1.2.115

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 ConcurrentModificationException error in Log4jContextFactory when canceling a registered callback while disposing an application.

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 header=false with bodyStartLineNumber.

SE-13440

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

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.

4.2.1 v1.3.8

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.

4.1.6 v1.2.83

Issue Description

SE-16282

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

4.1.5 v1.2.81

Issue Description

SE-16282

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

EE-7097/SE-11533

Fixed a problem in which a console log message displayed two lines for the same completed batch job.

SE-17812

Fixed a problem that caused the following error:

No qualifying bean of type org.mule.runtime.module.extension.internal.runtime.client.strategy.ExtensionsClientProcessorsStrategyFactory.

3.8.7 v1.2.41

Issue Description

SE-17299

Resolved a message-access violation exception java.lang.IllegalStateException that occurred after the August 2020 monthly patch.

SE-7717

Fixed a problem that occurred while executing MUnit tests that failed when using a null-safe operator.

September 8, 2020

4.3.0 v1.2.74

Issue Description

MULE-18694/SE-16719

Resolved an issue that caused applications to fail due to memory consumption when referencing nested subflows (using <flow-ref>).

MULE-18666

Fixed an issue that caused a StackOverflowException error when using the following DataWeave script:

#[output application/json --- message]

MULE-18689/SE-16734

Corrected a memory leak referencing the following class in the runtime logs:

org.mule.runtime.core.privileged.exception.
TemplateOnErrorHandler$
OnErrorHandlerFluxObjectFactorytransactional

MULE-18682

Fixed a problem that caused a ClassNotFoundException after a policy upgrade affecting proxy applications.

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 RegistryLifecycleCallback logger so that it no longer prints the customer’s security key.

MULE-18542/SE-15818

Resolved a thread leak when redeploying an application that uses Anypoint Connector for Database (Database Connector) and references the Oracle JDBC driver.

MULE-18628/SE-16435

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

MULE-18623/SE-16933

Corrected a memory leak that occurred when using dynamic configurations.

SE-15453

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

SE-15249

Fixed DataWeave attribute selector not dispatching to the correct implementation.

SE-15362

Fixed NullPointerException in DataWeave’s XML module.

DW-184/SE-15834

Fixed DataWeave inferred types when the output is undefined storage to recalculate output.

SE-15894

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

SE-16462

DataWeave now parses single key-value pairs correctly when mixed with conditionals.

SE-16539

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

SE-16167

The DataWeave Avro module now correctly converts logical types.

AGW-4287/SE-16981

Fixed an issue that caused object-store deserialization errors when upgrading the internal version of Rate Limiting policy.

SE-17193

Fix a deployment issue that occurred for apps with multiple nested function calls, such as ++, in DataWeave.

SE-17270

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.

MULE-18604/SE-12900

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

4.2.2 v1.2.111

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 RegistryLifecycleCallback logger so that it no longer prints the customer’s security key.

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 #[ sequence inside a String value in Mule operations, such as Logger.

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 OutOfMemory errors, which occurred when the app didn’t explicitly nullify the payload at the end of the Foreach loop.

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 import tag with deployment properties, which prevented placeholders from being replaced.

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 OutOfMemoryError: Metaspace issue that occurred when running MUnit tests.

SE-13440

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

SE-14220

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

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.

4.2.1 v1.3.5

Issue Description

SE-16867

Fixed an issue with DataWeave that caused the following error:

You called the function 'AnonymousFunction' with these arguments

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 OutOfMemory errors, which occurred when the payload was not explicitly nullified at the end of the Foreach loop.

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 OutOfMemoryError: Metaspace issue that occurred when running MUnit tests.

4.2.0 v1.2.103

Issue Description

SE-17450

Fixed an issue in which a CloudHub app was unresponsive when deployed in the 4.2.0 08-17-2020 release.

SE-15624

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

MULE-18573/SE-15592

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

MULE-18047/MULE-18634

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

MULE-18164/SE-14610

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

MULE-18390

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

4.1.6 v1.2.81

Issue Description

MULE-18390

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

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-17647/SE-12720

Fixed an issue in which a domain redeployment didn’t honor the application status and incorrectly restarted apps that were stopped before the redeployment.

SE-13404

Fixed an issue with event processing that occurred when executing MUnit tests on apps using Mule server notifications.

SE-13429

Resolved an issue in which MUnit tests didn’t execute when using a Java class.

MULE-17096/SE-12340

Fixed a NullPointerException error that occurred when using a lazy initialization subflow with an Async scope.

4.1.5 v1.2.78

Issue Description

MULE-18390

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

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.

SE-12095

Fixed a problem in which MUnit didn’t invoke the Mock When processor within a Choice flow (the REST service was invoked instead).

SE-12167

Resolved an issue invoking MUnit mocks when using with-attributes with a custom REST connector.

SE-11241

Fixed MUnit test execution failures that occurred when using validation:all, which were caused by an internal NullPointerException.

MULE-16230/SE-10165

Resolved an issue with Maven 3.5.0 and later placeholders (${revision}, ${sha1}, and ${changelist}) when used with the MUnit Maven plugin.

MULE-16483/SE-10782

Fixed an issue with deleting the HTTP config dependency file when undeploying domains on Windows systems.

EE-7358/SE-12434

Fixed an issue with undeployment when deleting the application <app-name>-anchor.txt file on Windows systems.

EE-6830/SE-12284

Fixed an issue that marked tracking processors (tracking:custom-event and tracking:transaction) as KNOWN instead of OPERATION, which caused MUnit not to intercept them.

SE-9559

Fixed an issue in which redeployment failed when using the Mule Secure Configuration Properties Extension module on Windows systems.

August 17, 2020

4.3.0 v1.2.72

  • Fixed: Missing JVM and Infrastructure metrics in Anypoint Monitoring dashboards.

4.2.2 v1.2.109

  • Fixed: Missing JVM and Infrastructure metrics in Anypoint Monitoring dashboards.

4.2.1 v1.3.3

  • Fixed: Missing JVM and Infrastructure metrics in Anypoint Monitoring dashboards.

4.2.0 v1.2.101

  • Fixed: Missing JVM and Infrastructure metrics in Anypoint Monitoring dashboards.

3.9.4 v1.2.38

  • Fixed: Missing JVM and Infrastructure metrics in Anypoint Monitoring dashboards.

3.9.3 v1.3.65

  • Fixed: Missing JVM and Infrastructure metrics in Anypoint Monitoring dashboards.

3.9.2 v1.3.18

  • Fixed: Missing JVM and Infrastructure metrics in Anypoint Monitoring dashboards.

3.9.1 v1.3.33

  • Fixed: Missing JVM and Infrastructure metrics in Anypoint Monitoring dashboards.

3.8.7 v1.2.37

  • Fixed: Missing JVM and Infrastructure metrics in Anypoint Monitoring dashboards.

August 4, 2020

4.3.0 v1.2.68

  • Fixed incorrect behavior in which accessing message.message.exceptionPayload.info.Element returned null instead of an error. (MULE-18535/SE-16524)

  • SDK OAuth authorization code-flow references do not have a stereotype making it fail when executed from MUnit. (MULE-18528)

  • Resolved an issue in which when an object store expired, it loaded all deserialized entries into memory, doubling memory consumption. (MULE-18579)

  • Fixed an issue in which using inline proxy configuration in the OAuth module failed to create the requestConfig configuration. (MULE-18564)

  • 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-18569/SE-16282)

  • Fixed an issue in which the Cache scope in a cluster configuration did not effectively monitor the cache in the secondary node. (MULE-18548/SE-14272)

  • Resolved an IndexOutOfBoundsException error that occurred when handling a backpressure error in a source policy. (MULE-18545)

  • Fixed a problem that occurred when using a property placeholder on an import tag with deploymentProperties that caused the placeholders to not be replaced. (MULE-16688)

  • Fixed an issue in which a connector configuration using OAuth caused metadata-resolution problems. (MULE-18513)

  • Resolved an SDK regression in which the component reference in an operation chain was wrongly calculated. (MULE-18504)

  • Fixed an issue in which creating a scheduledThreadPool with a coreSize value of 0 could cause high CPU utilization. (EE-7381)

  • Fixed an issue in which DataWeave skipNullOn did not behave properly because the value null was ignored in maps. (SE-16468)

  • Removed unnecessary log messages that appeared when using dynamic objects in DataWeave. (SE-16915)

  • 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. (MULE-18196/SE-16894)

  • Updated to the latest operating system security patches.

4.2.2 v1.2.107

  • Resolved an issue in which when an object store expired, it loaded all deserialized entries into memory, doubling memory consumption. (MULE-18579)

  • Resolved a problem that led to memory leaks from plugins and apps that use the Scala language. (MULE-18288/SE-16676)

  • Fixed an issue in which setting -Dmule.classloading.verbose=true prevented MUnit tests from running due to an endless loop. (MULE-17814/SE-14021)

  • Resolved a problem when using Mule 4 on Windows in which MUnit tests failed postexecution, with the IOException: Unable to delete file error. (MULE-17862/SE-13617)

  • 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-18312/SE-13775)

  • Fixed a problem in which error mappings were not used when running an application with lazy initialization on MUnit. (MULE-18286)

  • Resolved a MuleRuntimeException error namespace already exists that occurred when running MUnit tests. (MULE-16965/MULE-17845/SE-13491)

  • Fixed an issue in which MUnit 2.2.1 failed to stop an artifact cleanly. (MULE-17726/SE-13425)

  • 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-13426)

  • 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. (SE-15892)

  • 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-17863/SE-13533)

  • Resolved a problem in which MUnit did not execute mocking for a custom REST connector with defined attributes. (MULE-16987/SE-12167)

  • Fixed an issue in which MUnit 2.2.1 was unable to mock a custom processor in a Try scope. (SE-14409)

  • 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-18569/SE-16282)

  • Optimized invocation of Anypoint Connector for NetSuite by reducing the number of getServerTime calls when executing a search operation. (MULE-16668/SE-15200)

  • Resolved the NoClassDefFoundError error that occurred when accessing com/google/common/collect/ImmutableMap while running MUnit tests. (MULE-17736/MTS-384/SE-14259)

  • Fixed an issue in which an application running on-premises and managed with Runtime Manager deleted the object store when redeployed. (MULE-17417/SE-12341)

  • 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-18284)

  • Fixed a serialization problem with policies using the Rate limit SLA policy. (MULE-18492/SE-16365)

  • 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. (MULE-18196/SE-16894)

  • Updated to the latest operating system security patches.

4.2.1 v1.2.12

  • Fixed a NullPointerException error that occurred when using a lazy initialization subflow with an Async scope. (MULE-17096)

  • Resolved a problem in which MUnit did not execute mocking for a custom REST connector with defined attributes. (MULE-16987/SE-12167)

  • 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-12193)

  • Fixed an issue in which an application could not be undeployed on Windows if the anchor file (%MULE_HOME%\apps_app-name_-anchor.txt) was deleted. (SE-12434)

  • Resolved a problem in which a Cache scope failed validation when the payload was empty when entering the scope. (SE-12743)

  • 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-17863/SE-13533)

  • Resolved a problem when using Mule 4 on Windows in which MUnit tests failed postexecution, with the IOException: Unable to delete file error. (MULE-17862/SE-13617)

  • Fixed a java.lang.IllegalStateException: Can’t create new contexts after factory is closed error that occurred when running MUnit test cases. (SE-13647)

  • 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-18569/SE-16282)

  • Fixed a problem in which a referenced subflow was not resumed after stopping and starting an application. (MULE-17341)

  • Fixed a file leak when retrieving the DataWeave transformation script from a file. (EE-6857)

  • Resolved an issue in which MUnit failed to test an application using batch processing with the Can’t create new contexts after factory is closed error. (EE-7072)

  • Fixed an issue that occurred when processing analytics events after policy disposal. (AGW-3409)

  • Updated to the latest operating system security patches.

4.2.0 v1.2.95

  • Resolved a problem in which a flow with lazy initialization was incorrectly initialized twice, resulting in the Cannot process event as 'flow' is stopped error. (MULE-16920)

  • Fixed a configuration error in which Anypoint Connector for AMQP was using the wrong version. (SE-11912)

  • Fixed a deployment problem in which an application using Anypoint Connector for JMS raised ClassCastException with the org.springframework.beans.factory.support.NullBean error. (SE-12247)

  • Resolved a NullPointerException error that occurred when running MUnit on an application using an async processor in a subflow. (SE-12340)

  • Fixed an issue in which an application could not be undeployed on Windows if the anchor file (%MULE_HOME%\apps_app-name_-anchor.txt) was deleted. (SE-12434)

  • Fixed a problem in which MUnit raised the Cannot load class com.saxonica.xqj.SaxonXQDataSource error. (SE-13178)

  • 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-18569/SE-16282)

  • Fixed a file leak when retrieving the DataWeave transformation script from a file. (EE-6857)

  • Updated to the latest operating system security patches.

3.9.4 v1.2.36

  • Fixed an issue in which Anypoint Monitoring incorrectly displayed HTTP 4xxx request responses. (AGW-4138)

  • Fixed a problem in which namespaces were not processed correctly when dynamically loading an externalized DataWeave script. (SE-15955)

  • Resolved an issue in which calling an Oracle stored procedure with a CLOB datatype parameter resulted in a Cannot bind stream to a ScrollableResultSet or UpdatableResultSet error. (SE-16343)

  • Updated to the latest operating system security patches.

3.9.3 v1.3.61

  • Fixed an issue in which Anypoint Monitoring incorrectly displayed HTTP 4xxx request responses. (AGW-4138)

  • Updated to the latest operating system security patches.

3.9.2 v1.3.16

  • Fixed an issue in which Anypoint Monitoring incorrectly displayed HTTP 4xxx request responses. (AGW-4138)

  • Updated to the latest operating system security patches.

3.9.1 v1.3.30

  • Fixed an issue in which Anypoint Monitoring incorrectly displayed HTTP 4xxx request responses. (AGW-4138)

  • Fixed a problem in which the Anypoint Connector for Web Service Consumer incorrectly added a MULE_CORRELATION_ID header. (SE-16477)

  • Resolved an issue in which using JSON Layout format to customize logging required jackson.core and jackson-databind dependencies. (MULE-14503)

  • Updated to the latest operating system security patches.

3.8.7 v1.2.35

  • Fixed an issue in which Anypoint Monitoring incorrectly displayed HTTP 4xxx request responses. (AGW-4138)

  • Fixed an issue in which enabling Insight caused a blank payload and created problems downstream in the application logic. (SE-16166)

  • Resolved a problem that resulted in a java.lang.IllegalStateException: Only owner thread can write to message. error when a notification handler accessed messages. (MULE-12266)

  • Resolved an issue in which using JSON Layout format to customize logging required jackson.core and jackson-databind dependencies. (MULE-14503)

  • Updated to the latest operating system security patches.

July 15, 2020

4.2.2 v1.2.93

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates. (AGW-4199)

  • Reverted MULE-18370 because it caused a key collision in the ManagedCursorProvider cache management. (MULE-18506/SE-16470)

  • Fixed an issue that occurred while moving corrupted domain object store files to the Garbage folder. (SE-13383)

  • Mule 4 no longer fails to stream all of the payload to the client. (SE-14012)

  • Fixed an issue in which the DataWeave stream failed to serialize. (SE-14114)

  • An application no longer fails to deploy if it uses the same custom name space as an applied custom policy. (SE-15056)

  • DataWeave now properly handles the #[ sequence inside a String value in Mule operations, such as Logger. (SE-15067)

  • The redundant char[] value generated by DataWeave modules no longer causes a large memory footprint and OutOfMemoryError error. (SE-15201)

  • Fixed DataWeave attribute selector not dispatching to the correct implementation. (SE-15249)

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

  • Fixed an issue that caused blocked threads. (SE-15800)

  • Fixed DataWeave inferred types when the output is undefined storage so that the output is recalculated. (SE-15834)

  • Fixed an OutOfMemoryError: Metaspace error on applications with multiple concurrent deployments and some redeployments. (SE-16095)

  • 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. (SE-16119)

  • Fixed an error on processing Apache AVRO logical types in DataWeave scripts. (SE-16167)

4.2.1 v1.2.99

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates. (AGW-4199)

  • Upgraded Object Store v2 plugin to 4.0.25.

  • Reverted MULE-18370 because it caused a key collision in the ManagedCursorProvider cache management. (MULE-18506/SE-16470)

  • Fixed an issue that occurred while moving corrupted domain object store files to the Garbage folder. (SE-13383)

  • Fixed an issue in which the DataWeave stream failed to serialize. (SE-14114)

  • DataWeave now properly handles the #[ sequence inside a String value in Mule operations, such as Logger. (SE-15067)

  • Fixed DataWeave inferred types when the output is undefined storage so that the output is recalculated. (SE-15834)

  • Fixed an OutOfMemoryError: Metaspace error on applications with multiple concurrent deployments and some redeployments. (SE-16095)

July 9, 2020

4.3.0 v1.2.44

  • Fixed an issue in which applications using APIkit and policies with the autodiscovery component incorrectly returned 500 instead of 404. (AGW-4211/SE-16370)

  • Resolved a problem generating XML when creating an artifact declaration that contains a platform-managed OAuth connection provider. (MULE-18454)

  • Fixed a NullPointerException issue on the XML SDK framework when a parameter that has both CONTENT and OPTIONAL values is empty. (MULE-18475/SE-16232)

  • Errors without location values no longer cause policy error handling to behave like a back-pressure error. (MULE-18491/SE-16370)

  • Reverted MULE-18370 because it caused a key collision in the ManagedCursorProvider cache management. (MULE-18506/SE-16470)

  • Fixed an issue that occurred while moving corrupted domain object store files to the Garbage folder. (SE-13383)

  • DataWeave now properly handles the #[ sequence inside a String value in Mule operations, such as Logger. (SE-15067)

  • Fixed a problem in which a custom policy that applied an outbound request changed the behavior of an API by clearing attributes. (MULE-18375/SE-15704)

  • Added support for escaped Char sequences on DataWeave settings. (SE-15918)

  • Fixed a problem that occurred when resolving DataWeave errors and processing the flow stack. (MULE-18458/SE-15925)

  • Fixed an application deployment failure with the loops not allowed error. (MULE-18439/SE-15995)

  • Fixed an issue that prevented debugging an application in Studio 7.5 and Mule runtime engine 4.3. (SE-16006)

  • Resolved an issue in which combining Cache and For Each scopes caused a java.lang.ArrayIndexOutOfBoundsException: 0 error during execution. (MULE-18462/SE-16038)

  • Fixed a regression with MUnit spy assertions (before-call and after-call) that was introduced in Mule 4.3.0. (MULE-18501/MULE-18500/SE-16088)

  • Fixed an OutOfMemoryError: Metaspace error on applications with multiple concurrent deployments and some redeployments. (MULE-18498/MULE-18480/SE-16095)

  • Fixed an issue with backslash-character processing when running Studio on Windows, which caused Test Connection in Anypoint Connector for File to fail when the Configuration property was present. (MULE-18453/SE-16119)

  • Fixed a NullPointerException error that occurred when using Anypoint Connector for Database in a Try scope and running it more than once. (MULE-18488/SE-16133)

  • Resolved the ClassCastException: java.lang.Integer cannot be cast to java.lang.Long error when using Anypoint Connector for Kafka. (MULE-18489/SE-16281)

  • Fixed a JSON payload with spaces after an array value failed in DataWeave’s in-memory parser. (SE-16292)

  • Resolved a problem accessing flow.name in DataWeave transformations. (MULE-18490/SE-16317)

  • Fixed a regression issue in Mule 4.3.0 when using the Rate Limiting - SLA-Based policy. (MULE-18492/SE-16365)

  • Fixed an application start-up error NoSuchBeanDefinitionException: No qualifying bean of type 'org.mule.extensions.java.internal.cache.JavaModuleLoadingCache' available. (SE-16379)

  • Resolved a problem processing DataWeave date expressions when calculating year differences. (SE-16381)

  • Fixed an issue in which DataWeave nested dynamic objects skipped elements. (SE-16389)

  • Cached DataWeave compiled expressions based on string script to avoid an out-of-memory issue on deployment. (SE-16431)

  • Fixed metadata that was not generated correctly when a <ROW> tag was duplicated. (MDM-106/SE-16066)

  • Corrected problems in which threads hung when using Anypoint Connector for Virtual Machine under load. (MULE-18431)

  • Resolved an issue in which polling source Scheduler components incorrectly restarted on reconnection. (MULE-18294)

  • Fixed a race condition that occurred when a thread looked for policies and invalidated the cache simultaneously. (MULE-18440)

  • Mule no longer creates a default policy manager for each applied policy. (MULE-18442)

4.2.2

Updates for version 4.2.2 are not currently available.

For more information, see the MuleSoft Support Portal.

4.2.1

Updates for version 4.2.1 are not currently available.

For more information, see the MuleSoft Support Portal.

4.2.0 v1.2.85

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates. (AGW-4199)

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

  • Fixed an issue in which a stack overflow error occurred on the rx package in applications under load. (SE-14663)

  • DataWeave now properly handles the #[ sequence inside a String value in Mule operations, such as Logger. (SE-15067)

  • Fixed an issue that caused a Cannot open a new cursor on a closed stream error that was introduced in the June patch version. (SE-16470)

4.1.6 v1.2.74

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates. (AGW-4199)

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

  • Fixed an issue that caused an Unexpected end-of-input at payload error while appending the payload to a file in /tmp. (SE-15689)

  • Fixed an issue that caused a Cannot open a new cursor on a closed stream error that was introduced in the June patch version. (SE-16470)

4.1.5 v1.2.72

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates. (AGW-4199)

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

  • Fixed an issue in which the DataWeave stream failed to serialize. (SE-14114)

  • Fixed an issue that caused an Unexpected end-of-input at payload error while appending the payload to a file in /tmp. (SE-15689)

  • Fixed an issue that caused a Cannot open a new cursor on a closed stream error that was introduced in the June patch version. (SE-16470)

4.1.4 v1.2.71

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates. (AGW-4199)

4.1.3 v1.2.65

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates. (AGW-4199)

4.1.2 v1.2.80

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates. (AGW-4199)

3.9.4 v1.2.26

  • A proxy no longer experiences an outage during redeployment in Runtime Fabric, with two replicas and a rolling update. (SE-13596)

  • Fixed a dbCreateStruct() performance regression between Mule 3.8.5 and Mule 3.9.4. (SE-15910)

  • Fixed an issue with the lookup() function incorrectly calling flows asynchronously. (SE-16329)

3.9.1 v1.3.21

  • Fixed an issue in which the Anypoint Connector for WMQ Listener stopped processing messages when Anypoint MQ was unavailable. (SE-14656)

  • Fixed an issue introduced in the 02-June update that caused the WSC Consumer to incorrectly add the MULE_CORRELATION_ID header. (SE-16477)

June 10, 2020

4.2.2 v1.2.73

4.2.1 v1.2.86

4.2.0 v1.2.78

4.1.6 v1.2.68

4.1.5 v1.2.66

  • Fixed an error that occurred when accessing Gatekeeper and Analytics policy templates. (AGW-4199)

June 2, 2020

4.3.0 v1.2.37

  • Fixed: Mule application no longer throws the wrong HTTP response status code when api-gateway:autodiscovery is enabled. (SE-15935)

  • Fixed: When using a logger to log a value, a result containing ##[ is no longer incorrectly reevaluated. (MULE-18421)

  • Fixed: Resolved ClassCastException when running an API using the Interception API. (MULE-18416)

  • Fixed: Error that occurred when an expression accessed a target-operation payload attribute. (MULE-18397)

  • Fixed: OutOfMemory error that mentioned running out of Metaspace when running MUnit tests. (MULE-18390)

  • Fixed: When an HTTP Listener is the source of the flow and 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. (MULE-18378)

  • Fixed: NullPointerException error that occurred when processing a request and all in-flight cursors were inappropriately closed. (MULE-18371)

  • Fixed: Issue that might rarely cause key collision with the ManagedCursorProvider cache. (MULE-18370)

  • Fixed: MULE:OVERLOAD exception was thrown when the first policy contained a Cache Scope and the second policy contained a Try Scope error handler. (MULE-18369)

  • Fixed: Problem that prevented an application from restarting after stopping it using Runtime Manager. (MULE-18364)

  • Fixed: A custom global error handler is no longer ignored when located after a failing flow. (MULE-18312)

  • Fixed: Race condition that occurred while disposing flows using a until-successful construct. (MULE-18306)

  • Fixed: Issue where a policy deployment failed under certain circumstances because the errorType could not be found when deploying a policy. (MULE-18284)

  • Fixed: Resolved open JAR file-leak when reading resources, such as keystore, while configuring TLS. (MULE-18264)

  • Fixed: OCSClient now supports configuring the API version of the service using the system property. (MULE-18255)

  • Fixed: Classloading issue when connectors that use third-party libraries are not able to load classes if they rely on loadClass(s,b) from CompositeClassLoader. (MULE-18244)

  • Fixed: When resolving dependencies, a mule service no longer includes the Test scope dependencies, which caused unnecessary service registrations. (MULE-18208)

  • Fixed: An application no longer fails to deploy if it has the same custom namespace as that of an applied custom policy. (MULE-18196)

  • Fixed: Resolved a possible stack overflow on RejectionCallbackExecutorServiceDecorator while trying to generate an XML response. (MULE-18179)

  • Fixed: Resolved concurrent subflow instantiation problem where the inner processors location was being corrupted. (MULE-18102)

  • Fixed: ObjectStoreToMapAdapter no longer throws exceptions when used or accessed concurrently. (MULE-18172)

  • Fixed: Batch job summary is no longer logged twice. (EE-7097)

  • Fixed: Issue in which DataWeave’s common subexpression elimination incorrectly reduced two expressions, ignoring middle nodes. (SE-15904)

  • Added: Optimized connection-pool validations to avoid excessive and costly checks. (MULE-16668)

  • Added: Optimized application deployments, resulting in performance improvements. (MULE-18310)

  • Added: Optimized FlowProcessMediator#policySuccessError to create a single router for all exceptions rather than one for each exception or error. (MULE-18205)

  • Added: Upgraded groovy dependency to version 3.0.2. (MULE-18202)

4.2.2 v1.2.65

  • Fixed: Mule-application deadlock when submitting parallel requests. (SE-13047)

  • Fixed: <bti:xa-data-source-pool> now works with XA transactions. (SE-13364)

  • Fixed: Problem with semantic versioning build-metadata when deploying an application. (SE-11087)

  • Fixed: maxConcurrency was not honored when using a flow reference. (SE-15269)

  • Fixed: Issue with an exception affecting class loading, even though the class existed in the dependencies using shared libraries. (SE-14245)

  • Fixed: Issue with moving corrupted domain object store files to the Garbage folder. (SE-13383)

  • Fixed: Proxy no longer experiences outage during redeployment in Runtime Fabric, with 2 replicas and rolling update. (SE-13596)

  • Fixed: Issue with a redundant char[] generated by DataWeave modules, which led to a large memory footprint and OutOfMemoryError. (SE-15201)

  • Fixed: Incorrect value obtained when accessing variables' content in complex transformations with loops. (SE-15592)

  • Fixed: NullPointerException in DataWeave’s XML module. (SE-15362)

  • Fixed: DataWeave regression in the index-based descendant selector so that it now behaves like version 2.2.1. (SE-15642)

  • Fixed: Usage of java.util.Timezone now works as expected in DataWeave. (SE-9907)

  • Fixed: DataWeave’s diff function, which was inverting the expected versus actual comparison. (SE-15970)

  • Added: DataWeave’s XML module now includes a new property to handle XML DTDs. (SE-15159)

  • Added: DataWeave’s XML module now includes a new property to handle escaping > characters. (SE-15453)

  • Added: Optimized a DataWeave performance issue when resolving a parent with type at the parser level. (SE-15741)

4.2.1 v1.2.76

  • Fixed: Incorrect value when accessing variables' content in complex transformations with loops. (SE-15592)

4.2.0 v1.2.75

  • Fixed: Issue with moving corrupted domain object store files to the Garbage folder. (SE-13383)

  • Fixed: Incorrect value when accessing variables' content in complex transformations with loops. (SE-15592)

  • Fixed: Unexpected state with the error handler org.mule.runtime.core.internal.event.EventContextDeepNestingException. (SE-15597)

  • Added: Upgraded Reactor version to 3.2.12. (MULE-17427)

4.1.6 v1.2.64

  • Fixed: Incorrect value when accessing variables' content in complex transformations with loops. (SE-15592)

4.1.5 v1.2.63

  • Fixed: Incorrect value when accessing variables' content in complex transformations with loops. (SE-15592)

3.9.3 v1.3.46

  • Fixed: Issue where APIKit failed to validate yyyy-m-d and yyyy-m-dThh:mi:ss date formats. (SE-12947)

  • Fixed: Proxy no longer experiences outage during redeployment in Runtime Fabric, with 2 replicas and rolling update. (SE-13596)

April 7 2020

4.2.2 v1.2.40

  • Fixed: RAML parser compatibility issue.

  • Fixed: Targeted security fix.

  • Added: Anypoint Monitoring enhancements.

4.2.1 v1.2.58

  • Fixed: RAML parser compatibility issue.

  • Fixed: Targeted security fix.

  • Added: Anypoint Monitoring enhancements.

4.2.0 v1.2.71

  • Fixed: RAML parser compatibility issue.

  • Fixed: Targeted security fix.

  • Added: Anypoint Monitoring enhancements.

4.1.6 v1.2.60

  • Fixed: RAML parser compatibility issue.

  • Fixed: Targeted security fix.

  • Added: Anypoint Monitoring enhancements.

4.1.5 v1.2.59

  • Fixed: RAML parser compatibility issue.

  • Fixed: Targeted security fix.

  • Added: Anypoint Monitoring enhancements.

4.1.4 v1.2.59

  • Fixed: RAML parser compatibility issue.

  • Fixed: Targeted security fix.

  • Added: Anypoint Monitoring enhancements.

4.1.3 v1.2.52

  • Fixed: RAML parser compatibility issue.

  • Fixed: Targeted security fix.

  • Added: Anypoint Monitoring enhancements.

4.1.2 v1.2.53

  • Fixed: RAML parser compatibility issue.

  • Fixed: Targeted security fix.

  • Added: Anypoint Monitoring enhancements.

3.9.4 v1.2.12

  • Fixed: RAML parser compatibility issue.

  • Fixed: Targeted security fix.

  • Added: Anypoint Monitoring enhancements.

3.9.3 v1.3.31

  • Fixed: RAML parser compatibility issue.

  • Fixed: Targeted security fix.

  • Added: Anypoint Monitoring enhancements.

3.9.2 v1.3.5

  • Fixed: RAML parser compatibility issue.

  • Fixed: Targeted security fix.

  • Added: Anypoint Monitoring enhancements.

3.9.1 v1.3.6

  • Fixed: RAML parser compatibility issue.

  • Fixed: Targeted security fix.

  • Added: Anypoint Monitoring enhancements.

3.8.7 v1.2.24

  • Fixed: RAML parser compatibility issue.

  • Fixed: Targeted security fix.

  • Added: Anypoint Monitoring enhancements.

March 18 2020

4.2.2 v1.2.34

  • Security fixes

4.2.1 v1.2.52

  • Security fixes

4.2.0 v1.2.65

  • Security fixes

4.1.6 v1.2.54

  • Security fixes

  • Fixed: Read timeout with API Gateways. [SE-15074]

4.1.5 v1.2.53

  • Security fixes

4.1.4 v1.2.52

  • Security fixes

4.1.3 v1.2.45

  • Security fixes

4.1.2 v1.2.48

  • Security fixes

3.9.4 v1.2.9

  • Security fixes

3.9.3 v1.3.27

  • Security fixes

3.9.2 v1.3.2

  • Security fixes

3.9.1 v1.3.3

  • Security fixes

3.8.7 v1.2.21

  • Security fixes

February 26 2020

3.9.3 v1.3.0

  • Fixed: X-MULE-DDOS-VIOLATION was incorrectly added. [SE-12611]

January 7 2020

4.2.2 v1.2.16

  • Fixed: Analytics Engine performance on API Gateway scenarios. [SE-14155]

4.2.1 v1.2.33

  • Fixed: Analytics Engine performance on API Gateway scenarios. [SE-14155]

November 27 2019

3.9.3 v1.3.1

  • Added: Readiness probe now verifies API policies are applied before reporting as ready.

3.9.2 v1.3.1

  • Added: Readiness probe now verifies API policies are applied before reporting as ready.

3.9.1 v1.3.2

  • Added: Readiness probe now verifies API policies are applied before reporting as ready.

November 15 2019

4.2.1 v1.2.31

  • Fixed: Anypoint MQ suddenly stops processing Message in Mule 4.2.1. [SE-13863]

4.2.0 v1.2.50

  • Fixed: Issue moving corrupted Domain object store files to Garbage folder. [SE-13383]

November 1 2019

4.2.1 v1.2.24

  • Fixed: Flow Backpressure error when running DataWeave transformation. [SE-12583]

  • Fixed: JWT policy not responding under load when a CPU_INTENSIVE operation is present in the application. [SE-13091]

4.2.0 v1.2.45

  • Fixed: Flow Backpressure error when running DataWeave transformation. [SE-12583]

  • Fixed: JWT policy not responding under load when a CPU_INTENSIVE operation is present in the application. [SE-13091]

3.9.3 v1.2.39

  • Fixed: Critical issue affecting runtimes.

3.9.2 v1.2.28

  • Fixed: Critical issue affecting runtimes.

3.9.1 v1.2.26

  • Fixed: Critical issue affecting runtimes.

3.8.7 v1.2.18

  • Fixed: Critical issue affecting runtimes.

October 28 2019

4.2.1 v1.2.22

  • Fixed: Java heap memory is not displayed in Ops Center with Installer 1.1.1571866618-0015ffd or later.

4.2.0 v1.2.43

  • Fixed: Java heap memory is not displayed in Ops Center with Installer 1.1.1571866618-0015ffd or later.

4.1.6 v1.2.30

  • Fixed: Java heap memory is not displayed in Ops Center with Installer 1.1.1571866618-0015ffd or later.

4.1.5 v1.2.38

  • Fixed: Java heap memory is not displayed in Ops Center with Installer 1.1.1571866618-0015ffd or later.

4.1.4 v1.2.42

  • Fixed: Java heap memory is not displayed in Ops Center with Installer 1.1.1571866618-0015ffd or later.

4.1.3 v1.2.31

  • Fixed: Java heap memory is not displayed in Ops Center with Installer 1.1.1571866618-0015ffd or later.

4.1.2 v1.2.28

  • Fixed: Java heap memory is not displayed in Ops Center with Installer 1.1.1571866618-0015ffd or later.

3.9.3 v1.2.38

  • Fixed: Java heap memory is not displayed in Ops Center with Installer 1.1.1571866618-0015ffd or later.

3.9.2 v1.2.27

  • Fixed: Java heap memory is not displayed in Ops Center with Installer 1.1.1571866618-0015ffd or later.

3.9.1 v1.2.25

  • Fixed: Java heap memory is not displayed in Ops Center with Installer 1.1.1571866618-0015ffd or later.

3.8.7 v1.2.17

  • Fixed: Java heap memory is not displayed in Ops Center with Installer 1.1.1571866618-0015ffd or later.

October 4 2019

4.2.1 v1.2.19

  • Fixed: Java heap memory is not displayed in Ops Center.

  • Fixed: A secure property value containing the "=" character is not applied to applications.

4.2.0 v1.2.36

  • Fixed: Java heap memory is not displayed in Ops Center.

  • Fixed: A secure property value containing the "=" character is not applied to applications.

4.1.6 v1.2.29

  • Fixed: Java heap memory is not displayed in Ops Center.

  • Fixed: A secure property value containing the "=" character is not applied to applications.

4.1.5 v1.2.36

  • Fixed: Java heap memory is not displayed in Ops Center.

  • Fixed: A secure property value containing the "=" character is not applied to applications.

4.1.4 v1.2.41

  • Fixed: A secure property value containing the "=" character is not applied to applications.

4.1.3 v1.2.29

  • Fixed: A secure property value containing the "=" character is not applied to applications.

4.1.2 v1.2.27

  • Fixed: A secure property value containing the "=" character is not applied to applications.

3.9.3 v1.2.36

  • Fixed: A secure property value containing the "=" character is not applied to applications.

3.9.2 v1.2.26

  • Fixed: A secure property value containing the "=" character is not applied to applications.

3.9.1 v1.2.24

  • Fixed: A secure property value containing the "=" character is not applied to applications.

3.8.7 v1.2.16

  • Fixed: A secure property value containing the "=" character is not applied to applications.

September 3 2019

4.1.6 v1.2.16

  • Added: Support for Runtime Fabric deployments

August 2 2019

4.2.0 v1.2.28

  • Fixed: Incompatibility issue affecting some applications using APIkit 1.2.4

July 31 2019

4.2.0 v1.2.27

  • Fixed: Security issue affecting runtimes.

4.1.5 v1.2.25

  • Fixed: Security issue affecting runtimes.

4.1.4 v1.2.38

  • Fixed: Security issue affecting runtimes.

4.1.3 v1.2.27

  • Fixed: Security issue affecting runtimes.

4.1.2 v1.2.26

  • Fixed: Security issue affecting runtimes.

3.9.3 v1.2.34

  • Fixed: Security issue affecting runtimes.

3.9.2 v1.2.24

  • Fixed: Security issue affecting runtimes.

3.9.1 v1.2.22

  • Fixed: Security issue affecting runtimes.

3.8.7 v1.2.14

  • Fixed: Security issue affecting runtimes.

July 1 2019

4.2.0 v1.2.17

  • Fixed: CorrelationId is not included in application log lines.

  • Fixed: Accept-Expression in Batch job not evaluated correctly. [SE-11666]

  • Fixed: APIKit validation error issue after version 1.1.9 [SE-11839]

4.1.5 v1.2.19

  • Fixed: CorrelationId is not included in application log lines.

  • Fixed: Accept-Expression in Batch job not evaluated correctly. [SE-11666]

  • Fixed: Batch job corrupted when debugging app. [SE-9826]

  • Fixed: IBM MQ listener receiving REPLY_TO queue header message unable to reconnect after the queue manager restarts. [SE-11261]

4.1.4 v1.2.27

  • Fixed: CorrelationId is not included in application log lines.

4.1.3 v1.2.20

  • Fixed: CorrelationId is not included in application log lines.

4.1.2 v1.2.20

  • Fixed: CorrelationId is not included in application log lines.

June 12 2019

4.2.0 v1.2.12

  • Added: Java 8u212

  • Fixed: Updating policy version not using correct policy JAR. [SE-12023]

4.1.5 v1.2.15

  • Added: Java 8u212

  • Fixed: Automated policy violation notifications not being sent. [AGW-2927]

  • Fixed: Updating policy version not using correct policy JAR. [SE-12023]

4.1.4 v1.2.23

  • Added: Java 8u212

  • Fixed: Automated policy violation notifications not being sent. [AGW-2927]

  • Fixed: Updating policy version not using correct policy JAR. [SE-12023]

4.1.3 v1.2.16

  • Added: Java 8u212

  • Fixed: Automated policy violation notifications not being sent. [AGW-2927]

4.1.2 v1.2.16

  • Added: Java 8u212

  • Fixed: Automated policy violation notifications not being sent. [AGW-2927]

3.9.2 v1.2.5

  • Added: Java 8u212

3.9.1 v1.2.8

  • Added: Java 8u212

3.8.7 v1.2.5

  • Added: Java 8u212

May 17, 2019

4.2.0 v1.2.2

  • Added: Support for Runtime Fabric deployments

4.1.5 v1.2.1

  • Added: Support for Runtime Fabric deployments

April 30, 2019

4.1.4 v1.2.1

This release includes the following enhancements:

  • Added: Anypoint Monitoring agent

4.1.3 v1.2.1

This release includes the following enhancements:

  • Added: Anypoint Monitoring agent

4.1.2 v1.2.1

This release includes the following enhancements:

  • Added: Anypoint Monitoring agent

3.9.2 v1.2.1

This release includes the following enhancements:

  • Added: Anypoint Monitoring agent

3.9.1 v1.2.1

This release includes the following enhancements:

  • Added: Anypoint Monitoring agent

3.8.7 v1.2.1

This release includes the following enhancements:

  • Added: Anypoint Monitoring agent

March 27, 2019

4.1.4 v1.1.14

This release includes the following fixes:

  • Added: Ability to consume secure properties

  • Added: Automatic API Gateway HTTP proxy configuration

4.1.3 v1.1.13

This release includes the following fixes:

  • Added: Ability to consume secure properties

  • Added: Automatic API Gateway HTTP proxy configuration

  • Fixed: Ability to send "Base64 Encoded client_id and client_secret" in Authorization header for authorization-code-grant-type [SE-9065]

  • Fixed: Unknown error on Object Store operation [SE-9285]

  • Fixed: Client Enforcement Policy throwing "No value present" error [SE-8736]

  • Fixed: SDK scopes process internal chains as blocking [SE-9315]

  • Fixed: Failure to process subflow with async scopes [SE-9395]

  • Fixed: Batch crashes with ArrayList of HashMap as input [SE-9437]

  • Fixed: Cannot open a new cursor on a closed stream using batch processing [SE-9472]

  • Fixed: Invalid Session ID on SFDC connector reconnnection attempt. [SE-9471]

  • Fixed: Invalid XML generated for artifact declaration [MULE-15835]

4.1.2 v1.1.5

This release includes the following fixes:

  • Added: Ability to consume secure properties

  • Added: Automatic API Gateway HTTP proxy configuration

  • Fixed: Unable to invoke a service using a WSDL with nested imports [SE-8362]

  • Fixed: Web Service Consumer ignores CDATA tag in Consume operation [SE-8643]

  • Fixed: Fixes DataWeave flatfile transformation returns empty payload [SE-8608]

  • Fixed: Fixes DefaultEventContext not cleaned up [SE-8526]

  • Fixed: Client Enforcement Policy throwing "No value present" error [SE-8736]

3.9.2 v1.1.9

This release includes the following fixes:

  • Added: Ability to consume secure properties

  • Added: Automatic API Gateway HTTP proxy configuration

  • Fixed: Partitioned object store does not delete partition folder [SE-10999]

  • Fixed: Hung thread in WMQ transport with synchronous processing strategy [SE-10743]

  • Fixed: XSD schemas being loaded multiple times cause delayed startup [SE-10529]

  • Fixed: ObjectDoesNotExistException on OAuth module [SE-10423]

  • Fixed: WMQ transport with synchronous processing strategy is not reconnecting [SE-10362]

  • Fixed: Throttling policy doesn’t clean its cache [SE-10534]

  • Fixed: Oracle type with CLOB field raises error [SE-10726]

  • Fixed: Database connector file descriptor leaks when processing large payloads [SE-11071]

  • Fixed: SFTP connector is not closing connections [SE-10977]

3.9.1 v1.1.15

This release includes the following fixes:

  • Added: Ability to consume secure properties

  • Added: Automatic API Gateway HTTP proxy configuration

  • Fixed: Hung thread in WMQ transport with synchronous processing strategy [SE-10743]

  • Fixed: API console RAML validation errors [SE-8773]

  • Fixed: RAML parser uncaught exception [SE-9228]

  • Fixed: OAuth2 provider not working when offline; support RestClient reconnection [SE-9455]

  • Fixed: Response encoding being replaced in Web Service Consumer [SE-9298]

  • Fixed: Payload expression transform error [SE-9452]

  • Fixed: Addressed deployment issue when using the IMAP reconnection strategy. [SE-9544]

  • Fixed: LIST command is not issued after reconnection in FTP transport [SE-9323]

  • Fixed: APIKit validation error doesn’t display the field name [SE-8727]

  • Fixed: XSD schemas being loaded multiple times cause delayed startup [SE-10529]

  • Fixed: WMQ transport with synchronous processing strategy is not reconnecting [SE-10362]

  • Fixed: Oracle type with CLOB field raises error [SE-10726]

  • Fixed: Database connector file descriptor leaks when processing large payloads [SE-11071]

3.8.7 v1.1.7

This release includes the following fixes:

  • Added: Ability to consume secure properties

  • Added: Automatic API Gateway HTTP proxy configuration

  • Fixed: Partitioned object store does not delete partition folder [SE-10999]

  • Fixed: Memory leak in XsltTransformer [SE-8522]

March 15, 2019

4.1.4 v1.1.8

This release includes the following fixes:

  • Fixed: Event instances were kept too long in the buffer [SE-9556]

  • Fixed: DataWeave stream is closed before being consumed in batch aggregator [SE-9836]

  • Fixed: Batch process not doing "on complete" step when results collection is empty [SE-9899]

  • Fixed: Invalid Session ID on SFDC connector reconnnection attempt. [SE-9471]

  • Fixed: 'Could not deserialize object' in cache component. [SE-9879]

  • Fixed: DataWeave stream closed intermittently in a batch process. [SE-9974]

  • Fixed: Amazon SQS connector shutdown exception. [SE-9149]

  • Fixed: Backpressure is not triggered by a saturated CPU_INTENSIVE thread pool. [SE-10078]

  • Fixed: Invalid XML generated for artifact declaration [MULE-15835]

  • Fixed: ProcessingStrategy internal bufferSize is always 256 for flow-ref [SE-10226]

  • Fixed: IdempotentRedeliveryPolicy blocks CPU_LITE thread [SE-10306]

  • Fixed: Source error callback is not called when an error is caught in error handler [SE-10212]

  • Fixed: Gatekeeper policy causes memory leak on policy engine [SE-10641]

  • Fixed: Salesforce Marketing connector throws token expired exception [SE-10343]

  • Fixed: Context does not contain key error shown in the logs [SE-10867]

  • Fixed: Feedback Loop not working impacts on DoS policy behavior [AGW-2956]

Feburary 11, 2019

4.1.4

This release includes the following fixes:

  • Added: Support for viewing and alerting on heap memory metrics.

  • Added: Java 8u191

4.1.3

This release includes the following fixes:

  • Added: Support for viewing and alerting on heap memory metrics.

  • Added: Java 8u191

4.1.2

This release includes the following fixes:

  • Added: Support for viewing and alerting on heap memory metrics.

  • Added: Java 8u191

4.1.1

This release includes the following fixes:

  • Added: Support for viewing and alerting on heap memory metrics.

  • Added: Java 8u191

3.9.1

This release includes the following fixes:

  • Added: Support for viewing and alerting on heap memory metrics.

  • Added: Java 8u191

3.8.7

This release includes the following fixes:

  • Added: Support for viewing and alerting on heap memory metrics.

  • Added: Java 8u191

Was this article helpful?

💙 Thanks for your feedback!