Contact Us 1-800-596-4880

CloudHub Runtime and Operating System Patch Update Release Notes

These release notes describe monthly date-patch updates to Mule runtime engine and security updates to the underlying operating system for CloudHub.

In addition to these release notes, see:

MuleSoft Commerce Cloud Schedule

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

Month Release Available Sandbox Environment Auto-Update Production Environment Auto-Update

May

May 7

May 20-24

May 25-26

April

April 9

April 22-26

April 27-28

March

March 5

March 18-23

March 23-24

February

February 6

February 19-23

February 24-25

MuleSoft Government Cloud Schedule

The following table shows the current schedule for Government Cloud updates.

Month Release Available Sandbox Environment Auto-Update Production Environment Auto-Update

May

May 7

May 20-24

May 25-26

April

April 9

No Auto Update

No Auto Update

March

March 12

No Auto Update

No Auto Update

The release notes for an update are published in the same week in which the runtime patch is released for all Mule versions on CloudHub.

All releases occur in GMT-3 time. All automatic updates occur in the local time zone of the app’s deployment region. For example, CloudHub applies updates to apps deployed in the Asia-Pacific (Sydney) region in the AEST time zone and to apps deployed in the US West region in the PST time zone.

For the upcoming May 2024 Government Cloud Auto Update schedule, check these Knowledge Base Articles:

March 5, 2024

Fixed Issues

4.6.1 Runtime Updates

For Mule runtime 4.6.1, the image names that correspond with these fixes are 4.6.1:4 (LTS) and 4.6.1:4e (Edge).

Issue Resolution ID

Mule

Performance is now improved for certain For Each scenarios.

W-14678431

HTTP Request Connector no longer throws Connection limit exceeded, cannot process request when maxConnections is set to 1.

W-14686211

Disabling the enableNotifications flag on the On Error Continue component now works as expected.

W-14954677

Multi-step batch jobs can now be correctly resumed and finished after being stopped.

W-14726677

The error message is now improved for exceptions that occur when loading an extension because of Java version incompatibility.

W-14934626

The error message namespace already exists is no longer thrown when using the same namespace with the current module or extension namespace for apps using the XML SDK component.

W-14559071

Transactions' timeout is now honored. When a transaction times out, it is rolled back, and an error is thrown that can be handled with error handling. To enable this, activate the mule.tx.error.when.timeout feature flag.

W-14128870

Memory leaks no longer occur when using the mule-scripting-module dependency with HTTP Connector.

W-14479158

Java JDK inlineDeclaration now resolves correctly for stateless subtypes.

W-14645134

DataWeave

Performance is now improved when coercing addition and subtraction operations.

W-14927555

4.5.3 Runtime Updates

For Mule runtime 4.5.3, the image name that corresponds with these fixes is 4.5.3:8e.

Issue Resolution ID

Fixed OS security vulnerabilities.

N/A

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20240219

Issue Resolution ID

Performance is now improved for certain For Each scenarios.

W-14678431

HTTP Request Connector no longer throws Connection limit exceeded, cannot process request when maxConnections is set to 1.

W-14686211

Disabling the enableNotifications flag on the On Error Continue component now works as expected.

W-14954677

Multi-step batch jobs can now be correctly resumed and finished after being stopped.

W-14726677

Transactions' timeout is now honored. When a transaction times out, it is rolled back, and an error is thrown that can be handled with error handling. To enable this, activate the mule.tx.error.when.timeout feature flag.

W-14128870

4.3.0 Runtime Updates

  • MUnit distribution ID that corresponds with these fixes: 4.3.0:20231026-9.

Issue Resolution ID

Fixed OS security vulnerabilities.

N/A

February 16, 2024

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20240215.

  • This patch update reverts the fixes for the following issue: W-14809031.

Issue Resolution ID

DataWeave

Performance is now improved when coercing addition and subtraction operations.

W-14927555

February 6, 2024

What’s New

4.5.3 Runtime Updates

  • For Mule runtime 4.5.3, the image name that corresponds with this release is 4.5.3:5e.

3.9.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

Runtime Manager Agent versions included in Runtime 3.9.5, 4.3.0, 4.4.0, 4.5.0, and 4.6.0

This release of Runtime 3.9.5 includes Runtime Manager Agent 1.15.13. Runtime 4.3.0 and 4.5.0 include Runtime Manager Agent 2.5.9. Runtime 4.4.0 and 4.6.0 include Runtime Manager Agent 2.6.0.

Fixed Issues

4.6.0 Runtime Updates

For Mule runtime 4.6.0, the image names that correspond with these fixes are 4.6.0:40e (Edge) and 4.6.0:40 (LTS).

Issue Resolution ID

Mule

aspectj is now removed from distribution.

W-13913357

The Joda-Time library is upgraded to version 2.12.5.

W-13913362

The GraalJS library is upgraded to 22.3.3.

W-13961780

MUnit no longer fails with apps using Anypoint Connector for DotNet (DotNet Connector).

W-14747448

NullPointerException no longer occurs in XSD parsing when a schema has a minVersion/maxVersion.

W-14748090

Timeout is not considered for local transactions and rollbacks are silently executed.

W-14608096

MediaType cache now has a maximum size to prevent leaks.

W-14490182

DataWeave now uses objects as part of the Mule API.

W-14185880

License installation no longer fails with FileNotFoundException.

W-14542349

Legacy properties builder no longer reevaluates from root resolver placeholders.

W-14616618

JAVA_HOME is now properly handled by Surefire.

W-12082402

HTTP Redirect no longer works on Mule runtime 4.x on HTTP Post.

W-14619216

Race condition no longer results in NullPointerException when the Write Queue is full.

W-14543363

Container of the Embedded Runtime no longer stops if it wasn’t created.

W-14321634

Unnecessary MBeans for JMX management are no longer registered.

W-12422473

Internal dependency graph is now generated only once for all validations.

W-12421187

Extension model parsing no longer fails for extensions with dependencies declared as provided.

W-14646484

DataWeave

Caching now works correctly when coercing for addition and subtraction operations.

W-14591653

do scope declarations with pattern matching now properly reflect variable names when variables are optimized with common subexpression elimination.

W-14514837

The minInflateRatio property is now added to Excel format to control the zip bomb check threshold.

W-14315728

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20240122

Issue Resolution ID

Mule

Analytics Events and Policy Violations logging are now enabled.

W-14237017

Unapplied policy template deletion on startup is now enabled.

W-14407626

Native library dependencies are correctly loaded.

W-14497761

Fixed a leak when using expressions in parameters in OAuth Client Credentials configurations in connectors.

W-14391247

Timeout is now honored for local transactions.

W-14809031

An extra message field is now added when logging a message variable.

W-14723809

Timeout is now considered for local transactions and rollbacks are silently executed.

W-14608096

An extra message field is no longer added in the logs when logging the message variable.

W-14457630

DataWeave

Caching now works correctly when coercing for addition and subtraction operations.

W-14591653

do scope declarations with pattern matching now properly reflect variable names when variables are optimized with common subexpression elimination.

W-14514837

3.9.5 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.5-20240122

Issue Resolution ID

An XML transformation error no longer occurs when using the M-Dmule.xstream.allowlist flag.

W-14417598

January 9, 2024

What’s New

3.9.x, 4.3.0, 4.4.0, and 4.5.3 Runtime Updates

  • Updated to the latest operating system security patches.

Runtime Manager Agent versions included in Runtime 3.9.5, 4.3.0, 4.4.0, and 4.5.0

This release of Runtime 3.9.5 includes Runtime Manager Agent 1.15.13, and Runtime 4.3.0, 4.4.0, and 4.5.0 include Runtime Manager Agent 2.5.9.

Fixed Issues

4.5.3 Runtime Updates

For Mule runtime 4.5.3, the image name that corresponds with these fixes is 4.5.3:4e.

Issue Resolution ID

Mule

An issue with explicit socket connection timeout for socket creation was fixed.

W-14555248

Using mule-scripting-module with HTTP connector in a Mule app no longer causes a memory leak.

W-14479183

Using Salesforce Marketing Cloud connector no longer causes a memory leak.

W-14391247

XML SDK no longer fails to replace a complex parameter with a property value.

W-13681772

GroovyResourceReleaser is now enabled for each JDK. The incorrect cleaning method was removed.

W-14350781

okio-jvm is updated from version 3.2.0 to 3.6.0.

W-14261144

The nonProxyHosts setting now works correctly for HTTP Connector.

W-14161865

DataWeave

An issue with ndson data format loading was fixed.

W-14471869

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20231211

Issue Resolution ID

Hazelcast is upgraded to 5.2.4.

W-14404918

An issue with explicit socket connection timeout for socket creation with the management plane was fixed.

W-14555248

XML SDK no longer fails to replace a complex parameter with a property value.

W-13681772

The nonProxyHosts setting now works correctly for HTTP Connector.

W-14161865

November 28, 2023

What’s New

3.9.x, 4.3.0, 4.4.0, and 4.5.2 Runtime Updates

  • Updated to the latest operating system security patches.

Runtime Manager Agent versions included in Runtime 3.9.5, 4.3.0, 4.4.0, and 4.5.0

This release of Runtime 3.9.5 includes Runtime Manager Agent 1.15.13, and Runtime 4.3.0, 4.4.0, and 4.5.0 include Runtime Manager Agent 2.5.8.

Fixed Issues

4.5.2 Runtime Updates

For Mule runtime 4.5.2, the image name that corresponds with these fixes is 4.5.2:2e.

  • No new fixes are included.

November 13, 2023

Fixed Issues

4.5.2 Runtime Updates

For Mule runtime 4.5.2, the image name that corresponds with these fixes is 4.5.2:1e.

Issue Resolution ID

This patch update reverts the fix.

W-13681772

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20231110-1

Issue Resolution ID

This patch update reverts the fix.

W-13681772

November 7, 2023

What’s New

3.9.x, 4.3.0, 4.4.0, and 4.5.1 Runtime Updates

  • Updated to the latest operating system security patches.

Runtime Manager Agent versions included in Runtime 3.9.5, 4.3.0, 4.4.0, and 4.5.0

This release of Runtime 3.9.5 includes Runtime Manager Agent 1.15.13, and Runtime 4.3.0, 4.4.0, and 4.5.0 include Runtime Manager Agent 2.5.6.

Fixed Issues

4.5.1 Runtime Updates

For Mule runtime 4.5.1, the image name that corresponds with these fixes is 4.5.1:3e.

Issue Resolution ID

Mule

The org.json.json library is upgraded to 20231013.

W-14347983

The org.apache.santuario.xmlsec library is upgraded to 2.3.4.

W-14347988

The org.bouncycastle.bcprov-jdk15on library is upgraded to 1.74.

W-14351263

The Error Handler with attribute logException=false no longer logs the exception when using the Scheduler component.

W-13881167

The error A ByteBuffer Provider is already registered with name 'org.mule.weave.v2.memory.service no longer occurs.

W-13969259

Mule runtime no longer fails to start in Linux if the path contains spaces.

W-14321178

The Element DSL is available in the exceptionPayload attribute.

W-14067135

OutOfMemoryError no longer occurs after multiple redeployments of applications with the Scripting module and Groovy.

W-13038823

XML SDK no longer fails to replace a complex parameter with a property value.

W-13681772

DataWeave

Temporary files are now closed for inputs bigger than 1.5 MB.

W-13868202

The cached function coercion now works correctly for a second time when an argument is constant.

W-13763138

The DataWeave sum function with a single numeric string arg now returns Number type instead of String.

W-14086694

Reading Avro schema with an array of enum type items no longer returns an error.

W-14252745

Inconsistent XML encoding detection no longer occurs between indexed and in-memory parsers.

W-13805995

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20231026

Issue Resolution ID

Mule

The org.bouncycastle.bcprov-jdk15on library is upgraded to 1.74.

W-14351263, W-14347982

The org.json.json library is upgraded to 20231013.

W-14347983

The org.apache.santuario.xmlsec library is upgraded to 2.3.4.

W-14347980

The Error Handler with attribute logException=false no longer logs the exception when using the Scheduler component.

W-13881167

Multiple redeployments of applications linked to a domain project sharing IBM MQ Connector now works as expected.

W-12388528

The Element DSL is now available in the exceptionPayload attribute.

W-14067135

XML SDK no longer fails to replace a complex parameter with a property value.

W-13681772

DataWeave

The cached function coercion now works correctly for a second time when an argument is constant.

W-13763138

The DataWeave sum function with a single numeric string arg now returns Number type instead of String.

W-14086694

Reading Avro schema with an array of enum type items no longer returns an error.

W-14252745

Inconsistent XML encoding detection no longer occurs between indexed and in-memory parsers.

W-13805995

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20231026

Issue Resolution ID

The org.apache.santuario:xmlsec library is upgraded to 2.3.4.

W-14358602

Multiple redeployments of applications linked to a domain project sharing IBM MQ Connector now works as expected.

W-12388528

OutOfMemoryError no longer occurs after multiple redeployments of applications with Scripting module and Groovy.

W-13038823

October 12, 2023

What’s New

3.9.x, 4.3.0, 4.4.0, and 4.5.0 Runtime Updates

  • Updated to the latest operating system security patches.

October 3, 2023

What’s New

4.5.0 Runtime Updates

3.9.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

Runtime Manager Agent versions included in Runtime 3.9.5, 4.3.0, and 4.4.0

This release of Runtime 3.9.5 includes Runtime Manager Agent 1.15.13, and Runtime 4.3.0 and 4.4.0 include Runtime Manager Agent 2.5.5.

Fixed Issues

4.5.0 Runtime Updates

For Mule runtime 4.5.0, the image name that corresponds with these fixes is 4.5.0:23e.

Issue Resolution ID

Mule

Application name and flow name now appear inside the cache scope thread.

W-11818064

Deadlock in batch now works properly when a step fails because of max errors.

W-11702225

SubTypeMappings no longer define the same mapping twice.

W-11294196

StackOverflowError no longer occurs when there are recursive references in JsonTypeLoader.

W-11019412

An event no longer gets stuck when using a Foreach scope with a map payload. If the app has minMuleVersion >= 4.5.0 or if you are using the system property -M-Dmule.foreachRouterRejectsMapExpressions=true, the runtime generates an exception with "Foreach does not support 'java.util.Map' with no collection expression" message. With minMuleVersion < 4.5.0, the check isn’t done to preserve backwards compatibility with 4.4.0 and 4.3.0.

W-12207110

JDBC/JMS driver-specific cleanup is now performed if the driver is declared as a sharedLibrary.

W-12204790

Startup script now gives higher priority to JAVA_HOME instead of PATH.

W-12082402

Classloader leak no longer occurs in MVEL optimizers.

W-11785664

Variable propagation no longer fails with nested error handlers.

W-11861131

All Javax libraries are replaced with the Jakarta equivalent.

W-13588773

jsoup is upgraded to 1.15.3.

W-11750619

SLF4J is upgraded to 2.0.

W-13104897

Byte Buddy is upgraded to 1.14.0.

W-12305504

LMAX disruptor is upgraded to 3.4.3.

W-13312374

FastUtil is upgraded to 8.5.11.

W-13312374

ram-parser-2 is upgraded to 1.0.44-10.

W-13031307

commons-lang3 is upgraded to 3.12.0.

W-12041669

Log4j is upgraded to 2.20.0.

W-13792545

Reactor Core is upgraded to 3.4.22.

W-11786499

org.json:json is upgraded to 20230227.

W-13019304

Commons IO is upgraded to 2.13.0.

W-13748743

Bouncy Castle is upgraded to 1.74.

W-13844863

Hazelcast is upgraded to 5.2.4.

W-14080816

Maven is upgraded to 3.9.4.

W-13665263

jsr305 is removed from the distribution.

W-13588824

com.sun.xml.bind.jaxb-core is removed from the distribution.

W-13517798

CGLib is removed from the distribution.

W-10815440

Groovy is removed from the distribution.

W-12525966

geronimo-j2ee-connector_1.5_spec is removed from the distribution.

W-13097247

DataWeave

The typeOf function now returns the underlying type value.

W-10648848

The lookup function is now deprecated.

W-12036895

Memory usage is now improved when using for each scope.

W-12245438

DataWeave now loads the Java class methods in deterministic order. Setting the property mule.dw.java_module_loader_deterministic_functions_ordering=false reverts the behavior.

W-13028728

Typed parameters validation now works properly when using generics.

W-10671626

Support is now added for negative Periods.

W-10989197

The onNull function now calls the right overload.

W-11327185

The literal type checking over escaped String is now improved.

W-11333111

The fromHex function is now improved to avoid carrying the base to be consistent with fromBase64 function.

W-11343563

The intersection of Object types at runtime now correctly matches the behavior of type checking phase.

W-11611304

Unnecessary materialization in pattern matching no longer occurs.

W-11698394

Trailing zeroes after the decimal point are now removed by default for JSON, YAML, CSV, and DataWeave formats. Setting minMuleVersion to 4.4.x or previous versions reverts the behavior.

W-11750379

The update operation dealing with Array and Object now works correctly when streaming is enabled.

W-12227568

The sum function now works correctly with an Array of non-numeric values.

W-12475183

The StackOverflow error on recursive function call with Object type argument no longer occurs.

W-13635914

The sqrt function now works correctly when working with floating point numbers.

W-11811398

The exception handling at sum, joinBy, dw::core::Arrays::countBy, and dw::core::Arrays::sumBy functions causing an invalid result is now removed. Setting the property com.mulesoft.dw.defaultOperator.disableExceptionHandling=true reverts the behavior.

W-12558946

The support for BOM marker on UTF-16 files is now improved.

W-12704857

The @Since annotation is now correctly processed in overloads. Setting the property mule.dw.functions.hide_based_on_language_level=false reverts the behavior.

W-12622236

A new set of functions is added to coerce a String to Date, DateTime, Time, or Number by a given format and locale. For example, dw::util::Coercions::toLocalDateTime.

W-12552422

The dw::core::Strings::unwrap function now works as expected.

W-12513180

The YAML module support for multiple documents is now improved.

W-12103386

The Java module support now avoids unnecessary input stream consumption.

W-12005692

The inferred type on Array now works correctly with conditional elements.

W-11404344

Pattern matching is now improved when dealing with Union types.

W-11590136

Ranges now support numbers without integer limitations.

W-11210592

Parsing of directives including comments now works correctly.

W-11132728

Type checking phase now works correctly over annotations.

W-11032792

DataWeave now ignores BOM marker on binary files.

W-10650435

The YAML module support of empty Object and empty Array is now improved.

DW-1093

Adding schema to Union types and others now works correctly.

DW-746

The function dw::core::Binaries::concatWith that allows the concatenation of two Binary values is now added.

DW-882

Tail recursive function recognition now works correctly when using the default operator.

DW-866

Coercion for Union and Literal type now works correctly.

DW-851

Data format resolver now works correctly to avoid unnecessary error messages.

SE-18503

Warning messages are now improved when coercing Union types.

DW-845

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20230918

Issue Resolution ID

Mule

OAuth token no longer fails to refresh leaving the source in an inconsistent state.

W-14029065

Parse Template no longer obtains a different output between 4.3.0 to 4.4.0.

W-13588449

Race conditions no longer occur in the Until Successful component when two until-successful elements are executed sequentially.

W-13858445

Log4j is upgraded to 2.20.0.

W-13792545

A memory leak in HTTP Service no longer occurs after a redirection.

W-13754230

DataWeave

System property com.mulesoft.dw.xml_writer.declareXmlNamespace has been included to manage adding implicit namespaces like xml in the XML writer.

W-11965399

Temporary files are now closed for inputs bigger than 1.5 MB.

W-13868202

Milliseconds information is now preserved when converting the java.util.Date type.

W-14002706

September 1, 2023

What’s New

This release includes security updates.

3.9.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

Runtime Manager Agent versions included in Runtime 3.9.5, 4.3.0, and 4.4.0

This release of Runtime 3.9.5 includes Runtime Manager Agent 1.15.13, and Runtime 4.3.0 and 4.4.0 include Runtime Manager Agent 2.5.4.

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20230822

Issue Resolution ID

Mule

BouncyCastle is upgraded to version 1.7.

W-13701827

The 'Expect: 100-Continue' header is now ignored in server responses and log warnings.

W-13806048

DataWeave

An invalid UUID logical type in Avro module now throws an exception as expected.

W-13943112

3.9.5 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.5-20230823

Issue Resolution ID

This release includes important security enhancements and fixes.

W-13916544

3.9.4 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.4-20230824

Issue Resolution ID

This release includes important security enhancements and fixes.

W-13916544

3.9.3 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.3-20230823

Issue Resolution ID

This release includes important security enhancements and fixes.

W-13916544

3.9.2 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.2-20230823

Issue Resolution ID

This release includes important security enhancements and fixes.

W-13916544

3.9.1 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.1-20230823

Issue Resolution ID

This release includes important security enhancements and fixes.

W-13916544

3.9.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.0-20230823

Issue Resolution ID

This release includes important security enhancements and fixes.

W-13916544

3.9.4 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.4-20230824

Issue Resolution ID

This release includes important security enhancements and fixes.

W-13916544

3.9.3 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.3-20230823

Issue Resolution ID

This release includes important security enhancements and fixes.

W-13916544

3.9.2 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.2-20230823

Issue Resolution ID

This release includes important security enhancements and fixes.

W-13916544

3.9.1 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.1-20230823

Issue Resolution ID

This release includes important security enhancements and fixes.

W-13916544

3.9.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.0-20230823

Issue Resolution ID

This release includes important security enhancements and fixes.

W-13916544

August 9, 2023

What’s New

3.9.5 Runtime Update

This release of Runtime 3.9.5 includes Runtime Manager Agent 1.16.0.

August 8, 2023

What’s New

3.9.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

Issue Resolution ID

Changed default TLS client configuration to TLSv1.2

W-13838603

  • Updated to the latest operating system security patches.

Runtime Manager Agent versions included in Runtime 3.9.5, 4.3.0, and 4.4.0

This release of Runtime 3.9.5 includes Runtime Manager Agent 1.15.13, and Runtime 4.3.0 and 4.4.0 include Runtime Manager Agent 2.5.3.

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20230724

Issue Resolution ID

Guava is upgraded to version 32.1.1-jre.

W-13701825

3.9.5 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.5-20230726

Issue Resolution ID

SnakeYAML is upgraded to version 2.0.

W-13506775

Hazelcast is upgraded to version 3.12.13.

W-13741059

July 14, 2023

Fixed Issues

3.9.x, 4.2.x, 4.3.0, and 4.4.0

Issue Resolution ID

The TLS client configuration for worker instances now works correctly.

W-13761353

July 4, 2023

What’s New

3.9.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

  • Upgraded JDK8 patch to OpenJDK v1.8.0_372.

Runtime Manager Agent versions included in Runtime 3.9.5, 4.3.0, and 4.4.0

This release of Runtime 3.9.5 includes Runtime Manager Agent 1.15.13, and Runtime 4.3.0 and 4.4.0 include Runtime Manager Agent 2.5.2.

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20230616

Issue Resolution ID

Mule

Kryo is upgraded to version to 4.0.3.

W-13498807

Context has been added to prevent policies' variables from being overridden in parallel scenarios.

W-13509911

Spring is upgraded to version 5.3.27.

W-13206644

Undeploying/redeploying multiple operation policies to the same non-blocking operations no longer fails when processing new events.

W-13563214

The POST request body is no longer sent in a GET redirect.

W-12594415

The java.lang.NullPointerException error no longer appears while refreshing an OAuth token.

W-12975498

OutOfMemoryError no longer appears when Mule applications are redeployed with Mule scripting and Groovy.

W-13038823

JCommander is upgraded to version 1.78.

W-13206643

java.lang.NullPointerException no longer appears when you create a user-defined metadata type.

W-13049851

DataWeave

Multipart reader performance is enhanced by using the proper input stream implementation.

W-13099773

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20230616

Issue Resolution ID

Kryo is upgraded to version 4.0.3.

W-13499198

The java.lang.NullPointerException error no longer appears while refreshing an OAuth token.

W-12975498

June 6, 2023

What’s New

3.9.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

Runtime Manager Agent versions included in Runtime 3.9.5, 4.3.0, and 4.4.0

This release of Runtime 3.9.5 includes Runtime Manager Agent 1.15.13, and Runtime 4.3.0 and 4.4.0 include Runtime Manager Agent 2.5.1.

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20230522

Issue Resolution ID

Mule

snakeyaml is upgraded to version 2.0.

W-12354025

jackson-core is upgraded to version 2.15.

W-13014584

StackOverflowError no longer occurs when processing a large map in a batch job.

W-13123339

DataWeave

Streaming support now works correctly for JSON.

W-11790958

May 11, 2023

Fixed Issues

4.3.0, 4.4.0

Issue Resolution ID

Addressed JVM performance degradation in 0.1 vCore workers.

W-13187208

May 2, 2023

What’s New

3.9.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

Runtime Manager Agent versions included in Runtime 3.9.5, 4.3.0, and 4.4.0

This release of Runtime 3.9.5 includes Runtime Manager Agent 1.15.13, and Runtime 4.3.0 and 4.4.0 include Runtime Manager Agent 2.5.1.

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20230417

Issue Resolution ID

Mule

Upgraded org.json:json from 20220924 to 20230227.

W-13012142

Added support for native library dependencies at Mule applications and domains.

W-11855052

Added a new method for CoreServiceClient.

W-12659177

This release displays the policy definition version.

W-12733032

DataWeave

Closing resources immediately after reading when using text/plain MIME type.

W-12398584

Incorrect trimming of whitespaces no longer occurs when reading XML content.

W-12528980

Fixed splitBy management of large strings so String and Regex options are consistent with each other.

W-12452407

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20230417

Issue Resolution ID

Added a new method for CoreServiceClient.

W-12659177

This release displays the policy definition version.

W-12733032

3.9.5 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.5-20230424

Issue Resolution ID

This release fixes runtime generated usage metrics.

W-12981071

3.9.4 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.4-20230424

Issue Resolution ID

This release fixes runtime generated usage metrics.

W-12981071

3.9.3 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.3-20230424

Issue Resolution ID

This release fixes runtime generated usage metrics.

W-12981071

3.9.2 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.2-20230424

Issue Resolution ID

This release fixes runtime generated usage metrics.

W-12981071

3.9.1 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.1-20230424

Issue Resolution ID

This release fixes runtime generated usage metrics.

W-12981071

3.9.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.0-20230424

Issue Resolution ID

This release fixes runtime generated usage metrics.

W-12981071

April 20, 2023

Fixed Issues

3.9.5

Issue Resolution

ID

Updated to CloudHub worker metrics.

W-12981071

April 4, 2023

What’s New

3.9.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest version of the underlying operating system.

Fixed Issues

4.4.0 Runtime Updates

Mule distribution ID that corresponds with these fixes: 4.4.0-20230320

Issue Resolution ID

Mule

Kryo Serializer now discards the microseconds value from a timestamp during the serialize and deserialize operation.

W-12516135

Second Scatter Gather router does not execute when it has a Try scope for each component that raises an error handler within.

W-10619784

First Successful router hangs with raise-error.

W-12552091

Batch Job no longer shuffles CSV column order in Mule 4.4.

W-12505969

Added Exception reached PS subscriber for error handler error on February 7, 2023 patch.

W-12535932

NullPointerException no longer occurs when adding a null value to the cookie header.

W-12666590

Added Groovy to the default allowed scripting languages for logging.

W-12708905

Scripts in logging configuration files are no longer supported by default.

W-12556954

This release fixes deadlock when redeploying with policies.

W-12622899

DataWeave

Added cache Java values evaluation to avoid consuming streams more than once.

W-12635909

4.3.0 Runtime Updates

Mule distribution ID that corresponds with these fixes: 4.3.0-20230320

Issue Resolution ID

Mule

Added Groovy to the default allowed scripting languages for logging.

W-12708905

Second Scatter Gather router does not execute when it has a Try scope for each component that raises an error handler within.

W-10619784

Parallel For Each gets stuck with global Error Handler operation.

W-12556497

Transactions in nested Try scope with global Error Handling.

W-12671732

Combinations of First Successful router and Raise Error component no longer causes executions to hang.

W-10619792 / MULE-19874

3.9.5 Runtime Updates

Mule distribution ID that corresponds with these fixes: 3.9.5-20230330

Issue Resolution ID

Mule

Mule runtime engine no longer fails to load the driver when there is a connection pool for a database.

W-12436154

Identity file passphrase is logged in error messages.

W-12450302

Mule runtime engine 3.9.5 versions now start on macOS with versions where the patch version is omitted.

W-12623414

March 14, 2023

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20230313

Issue Resolution ID

Mule

This patch update reverts the fix.

W-12161504

March 8, 2023

What’s New

3.9.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

Runtime Manager Agent versions included in Runtime 3.9.5, 4.3.0, and 4.4.0

This release of Runtime 3.9.5 includes Runtime Manager Agent 1.15.13, and Runtime 4.3.0 and 4.4.0 include Runtime Manager Agent 2.5.0.

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20230217

Issue Resolution ID

Mule

This release improves the behavior of chained subflows and XA Transactions that can lead to an application deadlock.

W-12128703

This release improves the handling of JDBC resources to prevent memory leaks on the redeployment of apps.

W-12460123

The with-correlation-id scope no longer modifies errors thrown by other components.

W-12439048

XML SDK modules now work as expected when using a raise-error inside of a subflow, which prevents an InitialisationException.

W-12377294

Log4j scripting now supports Nashorn languages by default.

W-12549148

Requests no longer fail with NullPointerException: value with applications referencing a global Error Handler.

W-12535932

The loggingVariables in batch job serialization now works as expected when upgrading Mule runtime version.

W-12411873

This release updates snakeyaml to version 1.33.

W-12429030

This release upgrades org.raml:raml-parser-2 to version 1.0.51.

W-11577522

This release updates org.json:json to version 20220924.

W-12450128

The log level for HTTP response stream was closed before being read but response streams must always be consumed was changed from WARNING to ERROR.

W-12245298

Cookie headers are now correctly aggregated during the redirect mechanism.

W-12161504

Requests no longer fail with NullPointerException with applications using invalid cookies.

W-12528819

DataWeave

Fixed IndexOutOfBoundsException that occurred when combining the usage of heap memory for internal buffering with a customized buffer size.

W-12247447

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20230217

Issue Resolution ID

DB Connector’s prepareArray and preparaStruct functions now work as expected when using them inside of a Scatter-Gather.

W-11932094

Requests no longer fail with NullPointerException: value with applications referencing a global Error Handler.

W-12535932

Log4j scripting now supports Nashorn languages by default.

W-12549148

This release updates snakeyaml to version 1.33.

W-12429030

This release updates org.json:json to version 20220924.

W-12450128

3.9.5 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.5-20230217

Issue Resolution ID

This release updates the version of json-schema-validator to be compatible with the version of jackson-databind.

W-11577522

Upgraded com.googlecode.libphonenumber from 8.0.0 to 8.11.1.

W-13161611

February 24, 2023

What’s New

4.4.0 Runtime Updates

  • This patch update reverts the fixes for the following issues: W-12245298 and W-12161504.

For guidance with the patching process, see Apply Patch Updates.

February 16, 2023

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20230123

Issue Resolution ID

The following scripting languages are now enabled for log4j: Nashorn, JS, JavaScript, ECMAScript.

W-12517872

Requests no longer fail with NullPointerException: value with applications referencing a Global Error Handler.

W-12535932

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20230123

Issue Resolution ID

The following scripting languages are now enabled for log4j: Nashorn, JS, JavaScript, ECMAScript.

W-12517872

February 7, 2023

What’s New

3.9.x, 4.1.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

Runtime Manager Agent versions included in Runtime 3.9.5, 4.3.0, and 4.4.0

This release of Runtime 3.9.5 includes Runtime Manager Agent 1.15.13, and Runtime 4.3.0 and 4.4.0 include Runtime Manager Agent 2.4.37.

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20230123

Issue Resolution ID

Mule

Applications with an XML SDK connector now deploy correctly.

W-12362157

Concurrency errors no longer occur when a flow is called multiple times using the lookup function.

W-12206167

The Error Handler now returns the Event Id and Processor as expected.

W-12245760

This release upgrades the log4j dependency to version 2.19.

W-12353440

This release upgrades the com.hazelcast:hazelcast dependency to version 3.12.13.

W-12354026

This release upgrades the Jackson Databind library to version 2.13.4.2.

W-12219126

This release upgrades the org.apache.cxf:cxf-core dependency to version 3.5.5.

W-12354008

Cookie headers are now correctly aggregated during the redirect mechanism.

W-12161504

The log level for HTTP response stream was closed before being read but response streams must always be consumed was changed from WARNING to ERROR.

W-12245298

CloudHub applications no longer fail when using Global Error Handlers with a default configuration.

W-12218381

The insecure connection configuration in the TLS Configuration truststore now works as expected.

W-10822938

HTTP API status code 422 now shows the correct reason phrase.

W-12293483

WSC connector with an HTTP Requester configuration no longer fails when using a domain project.

W-12129696

The Error Handler now returns the Event Id and Processor as expected.

W-11983138

Flow reference validations no longer fail when using XML SDK components that declare inner sub-flows during lazy initialization.

W-11681056

DataWeave

dw::core::Dates::atBeginningOfWeek now works correctly when the input DateTime is Sunday.

W-11940166

The new com.mulesoft.dw.javaSqlDateToDate system property enables mapping java.sql.Date to Date instead of DateTime.

W-12043162

The Resource already closed exception no longer occurs when using the write function with a value bigger than 1.5MB with Avro format.

W-12067821

Cacheable overloaded functions, such as then, now dispatch to the correct function definition when called multiple times.

W-12073562

The default behavior now works correctly when having a null value coming from the Mule runtime.

W-12166609

High memory usage no longer occurs when using the dw::core::Arrays::divideBy function with an in-memory Array as input.

W-12167313

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20230123

Issue Resolution ID

Applications with an XML SDK connector now deploy correctly.

W-12362157

The Error Handler now contains the Event Id and Processor when handling issues from an HTTP Requester.

W-12245765

WSC connector with an HTTP Requester configuration no longer fails when using a domain project.

W-12407839

This release upgrades the log4j dependency to version 2.19.

W-12353442

This release upgrades the org.apache.cxf:cxf-core library to version 3.5.5.

W-12354020

This release upgrades the`com.hazelcast:hazelcast` dependency to version 3.12.13.

W-12354026

CloudHub applications no longer fail when using Global Error Handlers with a default configuration.

W-12218381

The insecure connection configuration in the TLS Configuration truststore now works as expected.

W-10822938

You can now start Mule in FIPS mode using any security provider.

W-12060316

January 11, 2023

What’s New

4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20230111

Issue Resolution ID

Change mule.enable.byteBuddy.objectCreation default value to false. If set to true, it will prevent race conditions during parallel deployments.

W-11920598

January 10, 2023

What’s New

3.9.x, 4.1.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20230102

Issue Resolution ID

Mule

Race conditions, which can make deployments fail, no longer occur when running parallel deployments.

W-11920598

The Scatter-Gather router no longer throws the exception UnsupportedOperationException when variables are set by Db::prepareArray or Db::prepareStruct.

W-11932094

Distributed locks are now released properly when a policy is disabled.

W-11929632

The error Can’t perform operation on 'Object_store'. ObjectStore not initialized no longer occurs when a redelivery policy that points to an object store is declared as a top level element.

W-11985583

An issue that prevented access to the SecureContext of a policy inside of a Batch component no longer occurs.

W-11493901

Setting a variable with a null value inside a Batch Aggregator component no longer fails with a NullPointerException.

W-11825409

The use of HTTP Insecure mode in a connector no longer fails with a NullPointerException.

W-12049036

Authorization of the OAuth dance no longer hangs when a custom object store uses a Redis cache.

W-11410770

The Idempotent Validation filter now cascades object store exceptions. Using the filter on Mule version 4.4 or earlier requires the property mule.rethrowExceptionsInIdempotentMessageValidator=true.

W-11529823

The XML SDK’s implicit configuration creation is disabled by default.

W-12113550

A fix to IllegalArgumentException handling prevents events from getting stuck in a For Each scope when an expression evaluates to a Map.

W-12234425

This release upgrades JSON to version 20220924.

W-11834878

This release upgrades the Tanuki wrapper version to 3.5.51.

W-12068528

In API Gateway, SLA deletion no longer generates an inconsistent contract status.

W-11898295

DataWeave

The function dw::core::Dates::atBeginningOfHour now works as expected when an hour is represented as a single digit.

W-11620156

Escaped quote characters now work as expected in CSV Module.

W-12128349

The FlatFile module now provides a reader property, retainEmptyStringFieldsOnParsing, for handling fields that lack values. When set to true, this property makes the reader retain these fields and set their values to an empty string. The default behavior of the reader is to remove those fields.

W-12036336

Data payloads without line breaks no longer work when using lenient as the recordParsing property. The other options to recordParsing support records that lack line breaks. noTerminator is preferred for fixed-length records that lack a line break.

W-12472890

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20221212

Issue Resolution ID

Mule

Distributed locks are now released properly when a policy is disabled.

W-11929632

The error Can’t perform operation on 'Object_store'. ObjectStore not initialized no longer occurs when a redelivery policy that points to an object store is declared as a top level element.

W-11985583

Setting a variable with a null value inside a Batch Aggregator component no longer fails with a NullPointerException.

W-11825409

The use of HTTP Insecure mode in a connector no longer fails with a NullPointerException.

W-12049036

The Idempotent Validation filter now cascades object store exceptions. Using the filter on Mule version 4.4 or earlier requires the property mule.rethrowExceptionsInIdempotentMessageValidator=true.

W-11529823

The XML SDK’s implicit configuration creation is disabled by default.

W-12113550

The Tanuki wrapper is upgraded to 3.5.51.

W-12068528

DataWeave

The FlatFile module now provides a reader property, retainEmptyStringFieldsOnParsing, for handling fields that lack values. When set to true, this property makes the reader retain these fields and set their values to an empty string. The default behavior of the reader is to remove those fields.

W-12036336

Data payloads without line breaks no longer work when using lenient as the recordParsing property. The other options to recordParsing support records that lack line breaks. noTerminator is preferred for fixed-length records that lack a line break.

W-12472890

3.9.5 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.5-20221212

Issue Resolution ID

Mule

Brackets ([ ]) no longer appear around error messages. This change fixes an issue introduced in Mule 3.9.1.

W-11494657

The expressions cache is no longer the source of a null pointer exception (NPE) during the evaluation of an MVEL expression.

W-11494657

December 6, 2022

What’s New

3.9.x, 4.1.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

November 14, 2022

What’s New

4.3.0 and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20221111

Issue Resolution ID

Mule

Using the insecure="true" attribute of the trust-store no longer throws NullPointerException.

W-12049036

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20221111

Issue Resolution ID

Mule

Using the insecure="true" attribute of the trust-store no longer throws NullPointerException.

W-12049036

November 9, 2022

What’s New

3.9.x, 4.1.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Update to the operating system library required for CloudHub worker health checks.

November 8, 2022

What’s New

3.9.x, 4.1.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Update to the underlying operating system version.

Runtime Manager Agent versions included in Runtime 3.9.5, 4.3.0, and 4.4.0

This release of Runtime 3.9.5 includes Runtime Manager Agent 1.15.13, and Runtime 4.3.0 and 4.4.0 include Runtime Manager Agent 2.4.34.

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20221026

Issue Resolution ID

Mule

Flow executions containing a First Successful and a Raise Error no longer stop responding.

W-10619792

The insecure="true" attribute of the trust-store config is now honored when additional properties are defined. Use the system property mule.honour.insecure.tls.configuration=true to apply this behavior in Mule 4.4 or earlier.

W-10822938

Applications that depend on a domain to load resources no longer fail with a "Couldn’t find resource: neither on classpath or in file system" error.

W-11625237

Error mapping is no longer executed when an error occurs inside of an operation policy.

W-11861168

Applications with global functions no longer fail on startup with a ClassCastException error.

W-11603893

Transactions now honor the Transaction Timeout configured in the Try scope.

W-11741912

To avoid XML SDK implicit configuration creation, this release adds the system property mule.disableXmlSdkImplicitConfigurationCreation=true.

W-10634129

DataWeave

onNull functions now work as expected.

W-11865849

Instead of returning an empty array in some scenarios, iterating flat file arrays now work as expected.

W-11932440

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20221024

Issue Resolution ID

Mule

Applications that depend on a domain to load resources no longer fail with a "Couldn’t find resource: neither on classpath or in file system" error.

W-11625237

The insecure="true" attribute of the trust-store config is now honored when additional properties are defined. Use the system property mule.honour.insecure.tls.configuration=true to apply this behavior in Mule 4.4 or earlier.

W-10822938

Error mapping is no longer executed when an error occurs inside of an operation policy.

W-11861168

To avoid XML SDK implicit configuration creation, this release adds the system property mule.disableXmlSdkImplicitConfigurationCreation=true.

W-10634129

Transactions now honor the Transaction Timeout configured in the Try scope.

W-11741912

In API Gateway, SLA deletion no longer generates an inconsistent contract status.

W-11898295

DataWeave

This release includes only non-user-impacting changes.

4.2.2 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.2.2-20221027

This release includes only non-user-impacting changes.

4.2.1 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.2.1-20221027

This release includes only non-user-impacting changes.

4.2.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.2.0-20221027

This release includes only non-user-impacting changes.

4.1.6 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.1.6-20221028

This release includes only non-user-impacting changes.

4.1.5 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.1.5-20221027

This release includes only non-user-impacting changes.

4.1.4 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.1.4-20221027

This release includes only non-user-impacting changes.

4.1.3 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.1.3-20221027

This release includes only non-user-impacting changes.

4.1.2 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.1.2-20221027

This release includes only non-user-impacting changes.

4.1.1 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.1.1-20221102

This release includes only non-user-impacting changes.

October 4, 2022

What’s New

3.9.x, 4.1.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Update to the latest version of the underlying operating system.

Runtime Manager Agent versions included in Runtime 3.9.5, 4.3.0, and 4.4.0

This release of Runtime 3.9.5 includes Runtime Manager Agent 1.15.13, and Runtime 4.3.0 and 4.4.0 include Runtime Manager Agent 2.4.34.

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20220922

Description Issue

Mule

Improved memory consumption when using a global error handler.

W-11503016

HTTP connections no longer have a leak that prevents new connections from opening.

W-11622837

TransactionTimeout is now set correctly on XA Transactions, preventing stale connections.

W-11741912

Improved the compatibility of Microsoft SQL Server when using XA Transactions with Bitronix.

W-11228596

Improved the performance of the execution of source events.

W-11676440

This release adds a feature flag that disables the error suppression feature. Error suppression prevents components such as the Web Service Consumer connector and the Until Successful scope from reporting errors outside their namespaces. Use the system property mule.suppress.mule.exceptions=false to apply this change.

W-11308645

The "Listener successfully reconnected" message no longer appears when the application starts.

W-10983306

HTTP wire logging now provides the complete context of the request and response for 413 and 414 scenarios.

W-11410315

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20220922

Description Issue

Mule

Improved memory consumption when using global error handler.

W-11503016

HTTP connections no longer have a leak that prevents new connections from opening.

W-11622837

TransactionTimeout is now set correctly on XA Transactions, preventing stale connections.

W-11741912

Improved the compatibility of SQLServer when using XA Transactions with Bitronix.

W-11228596

DataWeave

The Could not read from file store caused by Negative seek offset error no longer occurs when transforming big XML files.

W-11620006

4.2.2 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.2.2-20220919

Description Issue

Mule

HTTP connections no longer have a leak that prevents new connections from opening.

W-11622837

3.9.5 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.5-20220920

Description Issue

Mule

Internal improvements and library upgrades.

W-11741243

September 6, 2022

What’s New

4.1.1 Runtime Update

  • Update to the latest version of the underlying operating system

3.9.x, 4.1.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

Runtime Manager Agent versions included in Runtime 3.9.5, 4.3.0, and 4.4.0

This release of Runtime 3.9.5 includes Runtime Manager Agent 1.15.12 (the same version that is in the last update), and Runtime 4.3.0 and 4.4.0 include Runtime Manager Agent 2.4.33.

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20220824

Description Issue

Mule

Applications using the latest Open JDK 11 version no longer produce invalid JVM vendor errors.

W-11265408

Tanuki wrapper upgraded from 3.5.45 to 3.5.50 to support M1 (ARM) architecture.

W-11242363

Applications no longer fail to start with a Prefix URI must be not blank error.

W-11627710

DataWeave

Visual Studio Code extension no longer breaks with binary input format in the test scenario inputs directory.

W-11507190

Namespace is now added on elements when previously used at a deeper structure level.

W-11349764

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20220824

Description Issue

Tanuki wrapper upgraded from 3.5.45 to 3.5.50 to support M1 (ARM) architecture.

W-11242363

Applications no longer fail to start with a Prefix URI must be not blank error.

W-11627710

XML SDK modules now support implicit configurations.

W-10634129

Log levels for successful source reconnections are now set to INFO.

W-11437305

Expired access tokens now refresh on connectors using OAuth2.

W-11535924

August 2, 2022

What’s New

3.8.x, 3.9.x, 4.1.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

3.8.7, 3.9.x, 4.3.0, and 4.4.0, 4.1.x and 4.2.x Runtime Updates

  • Upgraded JDK8 patch to OpenJDK v1.8.0_332.

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20220722

Description Issue

Mule

Global Error Handler configurations no longer roll back transactions that are not supposed to roll back.

W-11324527

CXF is upgraded to version 3.5.1.

W-11267666

Mule no longer duplicates lifecycle phases for global Error Handler configurations.

W-11117613

Error mapping now works while deploying a custom Header Injection policy.

W-11147961

Different ModuleException constructors now produce the same output messages.

W-11192984

Mule runtime no longer produces the following warning: "An expression value was given for parameter 'variableName' but it doesn’t support expressions".

W-10998630

Incorrect logs no longer appear for polling sources.

W-11398537

Caching issues no longer cause a policy to use data from the wrong operation and produce Element and Element DSL mismatches with the flow stack.

W-11403067

A memory leak no longer occurs when using JMS Connector with ActiveMQ.

W-10583584

Mule SDK now supports a List of java.math.BigDecimal/BigInteger parameters.

W-11348869

Log levels for successful source reconnections are now set to INFO.

W-11437305

The caching strategy no longer applies the lifecycle phases to the Object Store when it is defined in the domain.

W-11203794

HTTP_Request_configuration in Anypoint Connector for HTTP now honors proxy settings.

W-10863931

DataWeave

The message for the StackOverflow script compilation error is no longer hidden.

W-11215958

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20220725

Description Issue

Global Error Handler configurations no longer roll back transactions that should not roll back.

W-11324530

CXF is upgraded to version 3.5.1.

W-11267666

Mule no longer duplicates lifecycle phases for global Error Handler configurations.

W-11117613

Mule runtime no longer produces the following warning: An expression value was given for parameter 'variableName' but it doesn’t support expressions".

W-10998630

Caching issues no longer cause a policy to use data from the wrong operation and produce Element and Element DSL mismatches with the flow stack.

W-11403067

A memory leak no longer occurs when using JMS Connector with ActiveMQ.

W-10583584

Error mapping now works while deploying a custom Header Injection policy.

W-11147961

July 6, 2022

What’s New

3.9.x, 4.3.0, and 4.4.0 Runtime Updates

  • Rolled back JDK8 upgrade.

July 5, 2022

What’s New

3.8.x, 3.9.x, 4.1.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

3.9.x, 4.3.0, and 4.4.0 Runtime Updates

  • Upgraded to the latest JDK8 patch.

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20220622

Description Issue

Mule

MUnit tests no longer fail when referencing the mule.home reserved property within the application on Windows OS.

W-11193698

Spring upgraded from 5.3.18 to 5.3.21.

W-11300535

Jackson upgraded to 2.13.3.

W-11139348

MuleArtifactAstCopyUtils no longer leaves mutable collections in generated artifacts or components.

W-11208606

AbstractForkJoinRouter-based processors, such as Parallel For Each and Scatter-Gather routers, can now show detailed error information for their failed routes. Use the system property mule.detailedCompositeRoutingExceptionLog=true to apply this change.

W-10965130

When using an XML SDK component that declares inner flows, flow-ref validation no longer fails with a flow "does not exist" error message during lazy initialization deployment.

W-11267062

Applications connected to the API Gateway no longer receive maximum concurrency reached errors.

W-10917220

DataWeave

Writing binary values with the JSON writer no longer outputs the base of the values.

W-11326859

This release fixes Avro property handling.

W-11324418

This release improves handling of streams that do not declare a size.

W-11277575

Fix write function so Avro format can be handled.

W-11047202

This release improves handling of string values in XML format.

W-11273037

Object Store v2

A netty memory buffer issue in AsyncHttpClient no longer occurs in the Object Store v2 plugin.

W-11210176/SE-19542

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20220622

Description Issue

Mule

Spring upgraded from 5.3.18 to 5.3.21.

W-11300535

Jackson upgraded to 2.13.3.

W-11139348

DataWeave

This releases fixes Avro property handling.

W-11324418

The DataWeave Avro module now correctly converts logical types.

W-10981989/SE-16167

Object Store v2

A netty memory buffer issue in AsyncHttpClient no longer occurs in the Object Store v2 plugin.

W-11210176/SE-19542

4.2.2 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.2.2-20220622

Description Issue

Mule

Spring upgraded from 5.1.6 to 5.3.21.

W-10989650

DataWeave

This release fixes Avro property handling.

W-11324418

Object Store v2

A netty memory buffer issue in AsyncHttpClient no longer occurs in the Object Store v2 plugin.

W-11210176/SE-19542

4.2.1 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.2.1-20220622

Description Issue

Mule

Spring upgraded from 5.1.6 to 5.3.21.

W-10989650

DataWeave

This release fixes Avro property handling.

W-11324418

Object Store v2

A netty memory buffer issue in AsyncHttpClient no longer occurs in the Object Store v2 plugin.

W-11210176/SE-19542

4.2.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.2.0-20220622

Description Issue

Mule

Spring upgraded from 5.1.6 to 5.3.21.

W-10989650

DataWeave

This release fixes Avro property handling.

W-11324418

3.9.5 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.5-20220623

Description Issue

Mule

Jackson upgraded to 2.13.3.

W-11139348

June 7, 2022

What’s New

3.8.x, 3.9.x, 4.1.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

3.9.5, 4.3.0, and 4.4.0 Runtime Updates

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20220523

Description Issue

Mule

Mule no longer fails with error DefaultFeatureFlaggingService after applying the 2022 May patch.

W-11172835

File attributes are no longer removed when using Parallel For Each.

W-10848628

FIPS enabled Mule Clusters no longer throw a java.nio.BufferUnderflowException warning when using the RetrieveAll operation on an Object Store.

W-10884325

ValueProvider parameters validations now work properly when combined with TypeResolver annotations.

W-10634121

Updated the error message shown when a Batch component cannot queue records.

W-11086577

Added logging to AbstractQueueStoreDelegate to describe why a record was not successfully queued.

W-11086587

The AS400 connector now properly receives a JSON response instead of org.mule.runtime.core.internal.util.message.stream.UnclosableCursorStream.

W-11093225

Mule now raises an ExceptionNotification error when ExtensionMessageSource fails to start.

W-10619908

Deserializing older SDK models no longer causes a NullPointerException error.

W-10815920

Polling frequency now works correctly when using the value 60000, which was previously incorrectly interpreted to poll every 1 second rather than every 1 minute.

W-10682121

XML SDK modules now properly access configurations defined at the domain level.

W-10719167

Upgraded Spring dependency from 5.1.20 to 5.3.18.

W-10989650

Mule applications no longer crash due to an unhandled IllegalStateException error when processing a batch block.

W-10742153

Mule now fails as expected if the event source configuration for the application is incorrect.

W-10619908

Mule application deployment properties are no longer lost after domain redeployment.

W-10984029

A memory leak no longer occurs after redeploying multiple times an application that uses the IBM MQ connector.

W-10672197

Mule now supports deploying applications that define a listener-config name based on an application property.

W-10923083

Connector parameters are now received properly instead of being null.

W-10920842

DataWeave

DataWeave now parses Java objects without errors.

W-10832766

The text/plain reader now correctly ignores the byte order mark (BOM). The JSON writer now uses the encoding information available in Binary values when writing them as String values instead of using the writer configuration encoding. To restore the previous behavior, enable the system property com.mulesoft.dw.decode_binaries_with_writer_encoding.

W-10696255

Multiline string indentation on YAML now works correctly.

W-10955882

The FlatFile module now includes the allowLenientWithBinaryNotEndElement property to support existing behavior.

W-10935528

Fixed ClassCastException in multipart module.

W-10943884

DataWeave now shows a descriptive error when there is an unsupported output mime type.

W-10876534

The indexed XML reader no longer adds unnecessary text fields to XML objects.

W-10942171

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20220523

Description Issue

Mule

File attributes are no longer removed when using Parallel For Each.

W-10848628

FIPS enabled Mule Clusters no longer throw a java.nio.BufferUnderflowException warning when using the RetrieveAll operation on an Object Store.

W-10884325

The AS400 connector now properly receives a JSON response instead of org.mule.runtime.core.internal.util.message.stream.UnclosableCursorStream.

W-11093225

Added logging to AbstractQueueStoreDelegate to describe why a record was not successfully queued.

W-11086587

Updated the error message shown when a Batch component cannot queue records.

W-11086577

Mule now raises an ExceptionNotification error when ExtensionMessageSource fails to start.

W-10619908

Mule applications no longer crash due to an unhandled IllegalStateException error when processing a batch block.

W-10742153

Mule now fails as expected if the event source configuration for the application is incorrect.

W-10619908

Upgraded Spring dependency from 5.1.20 to 5.3.18.

W-10989650

Mule application deployment properties are no longer lost after domain redeployment.

W-10984029

A memory leak no longer occurs after redeploying multiple times an application that uses the IBM MQ connector.

W-10672197

DataWeave

The FlatFile module now includes the allowLenientWithBinaryNotEndElement property to support existing behavior.

W-10935528

DataWeave no longer throws exceptions when using the default operator with fromBase64.

W-10648825

May 24, 2022

What’s New

3.9.x, 4.1.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

May 9, 2022

What’s New

4.3.0 and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

May 3, 2022

What’s New

3.8.x, 3.9.x, 4.1.x and 4.2.x Runtime Updates

  • Updated to the latest operating system security patches.

Fixed Issues

4.2.2 Runtime Updates

Description Issue

Object Store v2 now includes support for HTTP Proxy in MuleSoft Government Cloud.

W-10735910

4.2.1 Runtime Updates

Description Issue

Object Store v2 now includes support for HTTP Proxy in MuleSoft Government Cloud.

W-10735910

3.9.5 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.5-20220428

Description Issue

APIKit now provides the ability to disable encoding detection.

W-10867010

Removed private logger with unexpected data formatting from the mule_ee.log file.

W-10967100

April 5, 2022

What’s New

3.8.x, 3.9.x, 4.1.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20220321

Description Issue

Race conditions no longer occur when running parallel deployments.

W-10672687/SE-23764

Custom connector POST requests no longer send the body as NULL when handling empty payloads.

W-10818822

The redirect implementation properly handles the "Preserve Header Case" configuration.

W-10822777

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20220321

Description Issue

Race conditions no longer occur when running parallel deployments.

W-10672687/SE-23764

Custom connector POST requests no longer send the body as NULL when handling empty payloads.

W-10818822

The redirect implementation properly handles the "Preserve Header Case" configuration.

W-10822777

March 8, 2022

What’s New

3.8.x, 3.9.x, 4.1.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

3.9.5, 4.3.0, and 4.4.0 Runtime Updates

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20220221

Description Issue

Mule

A direct memory error no longer occurs when the com.mulesoft.dw.directbuffer.disable system property is enabled.

SE-24186

Set-Cookie is now handled correctly after a redirect request.

W-10667387 / MULE-19942

Properties now resolve correctly for document attributes of the AST metadata.

W-10673280 / MULE-20090

Metadata type is no longer missing from the definition when present in the schema.

W-10674401 / SDK-48

When disposing of an application, Mule no longer throws an IOException error indicating that the underlying JAR file is in use.

W-10674436 / W-10674454 / SE-23775

After a failed HTTP request, applications no longer stop when reading the error payload in the error handler.

W-10681464 / MULE-19537

The warning Illegal reflective access by EfficientReflectionHashCode no longer occurs due to starting Mule when using JDK 11.

W-10730677 / EE-7990

LifecycleObjectSorter and dependency resolvers implemented in this release reduce application deployment time.

W-10745620 / W-10746222 / MULE-19984

Thread-local interference no longer occurs when a task is scheduled for execution on the same thread due to thread-pool exhaustion. One possible symptom was a transaction not being properly cleaned up under heavy load, followed by nested transaction errors.

W-10619599 / MULE-20072 / SE-24241

DataWeave

A direct memory error no longer occurs when the com.mulesoft.dw.directbuffer.disable system property is enabled.

SE-24186

Duplicate declarations for namespace prefixes in XML no longer occur.

W-10648792 / DW-1081

Exceptions are no longer thrown due to use of the default operator with fromBase64.

W-10648825 / SE-23812

Avro unions with enums are now supported.

W-10706991

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20220221

Description Issue

Mule

Set-Cookie is now handled correctly after a redirect request.

W-10667146 / MULE-19942

When disposing of an application, Mule no longer throws an IOException error indicating that the underlying JAR file is in use.

W-10674462 / SE-23775

After a failed HTTP request, applications no longer stop when reading the error payload in the error handler.

W-10681471 / MULE-19537

LifecycleObjectSorter and dependency resolvers implemented in this release reduce application deployment time.

W-10745606 / W-10746226 / MULE-19984

Thread-local interference no longer occurs when a task is scheduled for execution on the same thread due to thread-pool exhaustion. One possible symptom was a transaction not being properly cleaned up under heavy load, followed by nested transaction errors.

W-10619599 / MULE-20072 / SE-24241

3.9.5 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.5-20220222

Description Issue

Error responses now return in the correct format, in quotes instead of square brackets.

W-10660160 / SE-24398

February 8, 2022

What’s New

3.8.x, 3.9.x, 4.1.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20220124

Description Issue

Mule

Anypoint Connector for Box (Box Connector) no longer fails to recreate the input stream after an access token refresh, preventing a stream closed issue.

MULE-20001/SE-23666

A concurrent connection limitation in Anypoint Connector for NetSuite (NetSuite Connector) no longer occurs.

MULE-19937/SE-22359

The readiness check performed when deploying on Runtime Fabric is now processed correctly.

AGENT-466/SE-22948/SE-22585

Running multiple MUnit cases together no longer causes a No bean named '_muleDefaultObjectSerializer' available error.

MULE-20012/SE-23407

Anypoint Connector for Google Calendar (Google Calendar Connector) no longer overwrites the access_token, which prevents generating incorrect results.

MULE-20019/SE-23584

You can now use static values in a flow reference processor.

MULE-19987/SE-23634

Mule no longer performs a thread switch in a transactional context that uses multithread and the same cache-key.

EE-8216/SE-23816

Using a custom connector that includes enum types no longer prevents applications from deploying successfully.

MULE-19976/SE-24012

Mule no longer returns an incorrect CONNECTIVITY error type when a ConnectionException is thrown when using the Java SDK.

MULE-19895/SE-24091

Deploying a Mule application with unpaired namespaceUri in schemaLocations no longer causes an ArrayIndexOutOfBoundsException error.

MULE-20035/SE-24099

Global property values of a module are now accessible within a private operation that is invoked within a flow control component.

MULE-19962/MULE-19035/SE-22282

DataWeave

An endless loop issue no longer occurs when writing a CSV file with bufferSize=0.

DW-1074

Creating sample files using the binary type no longer causes an error.

DW-390

Corrected the documentation of the`Periods::between` function.

DW-1070

Upgraded some dependencies, including avro and jackson, and removed unused AWS dependencies (#1673).

DW-1080

Upgraded the edi-parser with SLF4J.

CONN-9598

Performing transformations from avro to other formats no longer causes an exception when the enum type field is present.

SE-23802

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20220124

Description Issue

Mule

Anypoint Connector for Box (Box Connector) no longer fails to recreate the input stream after an access token refresh, preventing a stream closed issue.

MULE-20001/SE-23666

A concurrent connection limitation in Anypoint Connector for NetSuite (NetSuite Connector) no longer occurs.

MULE-19937/SE-22359

The readiness check performed when deploying on Runtime Fabric is now processed correctly.

SE-22948/SE-22585

Running multiple MUnit cases together no longer causes a No bean named '_muleDefaultObjectSerializer' available error.

MULE-20012/SE-23407

Anypoint Connector for Google Calendar (Google Calendar Connector) no longer overwrites the access_token, which prevents generating incorrect results.

MULE-20019/SE-23584

Mule no longer returns an incorrect CONNECTIVITY error type when a ConnectionException is thrown when using the Java SDK.

MULE-19895/SE-24091

Mule no longer performs a thread switch in a transactional context that uses multithread and the same cache-key.

EE-8216/SE-23816

Global property values of a module are now accessible within a private operation that is invoked within a flow control component.

MULE-19962/MULE-19035/SE-22282

DataWeave

Corrected the documentation for the Periods::between function.

DW-1070

Upgraded the edi-parser with SLF4J.

CONN-9598

3.9.5 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.5-20220127

Description Issue

A race condition, which caused an incorrect schema validation, no longer occurs when deploying multiple applications in parallel.

MULE-20024/SE-22842

The CXF interceptor no longer adds an extra xml tag to some HTTP responses.

MULE-20043/SE-23853

Mule 3.8 and Mule 3.9 now behave the same when setting variables and their associated MIME type..

MULE-19814/SE-22635

HTTP requests that contain an encoded double slash in the URI parameter no longer cause a No listener found error.

MULE-19933/SE-22967

Adoptium Temurin JDK is now a recommended JDK vendor.

MULE-19917/SE-23354

Removing an application that is in stopped state no longer prevents redeploying that application.

MULE-19890/SE-22261

CXF components no longer throw exceptions when a mule-xml transformer is set after a CXF proxy with WS:Security.

MULE-19889/SE-21182

The Foreach component now uses the same correlationId for every iteration when setting system property mule.compoundCorrelationId.disable=true.

MULE-19844/SE-22632

Stopping a server in a server group no longer causes Anypoint Platform to show application status as Undeploying.

MULE-19783/SE-21872

Requests no longer remain stuck at the end of a request-reply scope.

MULE-19780/SE-21042

A ClassNotFoundException: Cannot load class 'scala.None$' error no longer occurs when serializing input streams data instead of the object.

EE-8140/SE-21240

January 11, 2022

What’s New

  • Updated the auto-update dates for the sandbox and production environments.

January 4, 2022

What’s New

3.8.x, 3.9.x, 4.1.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20211227

Description Issue

Mule

MUnit tests no longer fail after migration from Mule 4.2.1 to Mule 4.3.0 or higher versions.

MULE-19866/SE-21030

This release adds the mule.errorTypes.lax feature. When enabled, error types are enforced.

MULE-19879/SE-23207

MUnit no longer hangs as references to Spring schemas in the Mule XSD schema are removed.

MULE-19904/SE-23247

Applications that implement a VM Listener no longer raise java.lang.IllegalStateException: No connection has been bound errors and quit.

SE-22172

Application deployment no longer fails with Task [App].wsc-dispatcher rejected from Scheduler errors.

SE-22851

A null pointer exception error on ObjectBeanDefinitionCreator.processMuleProperties that prevented app deployment no longer occurs.

MULE-19886

FlowProcessMediator no longer leaks the payload of the first request.

MULE-19869

Mule no longer raises exception errors for a custom connector developed with Mule SDK for Java.

MULE-19936/SE-23408

If the redelivery policy is exhausted in a source configured with transactions, Mule no longer raises an error that runs in a loop.

MULE-19915

Processors in subflows now get the processing strategy of the root flow.

MULE-19924

Autogenerated Mule connectors no longer fail with NumberFormatException errors.

MULE-19871/SE-21463

You can now redeploy applications that were in a stopped state when they were deleted.

MULE-19890/SE-22261

DataWeave now escapes the \ symbol when used in combination with the " symbol.

MULE-19900/SE-22346

The batch processing On Complete phase no longer fails if it encounters an error stream.

EE-8020/SE-22386

Logs no longer show reconnection successful messages when reconnection attempts to the FTP server are exhausted because the server is unavailable.

SE-22434

Transactions opened by the JMS Listener are no longer rolled back.

MULE-19919/SE-23039

You can now perform parallel deployments of apps that are linked to a domain and share a configuration.

MULE-19912/SE-23123

Mule now recognizes Eclipse Temurin by Adoptium (formerly Adopt OpenJDK project) as a recommended JDK Vendor and no longer raises an INFO-level log message.

MULE-19917/SE-23354

Apache Commons Compress upgraded to version 1.21.

EE-8088

GSON upgraded to version 2.8.9.

EE-8154

Kryo updated to version 4.0.2.

EE-8153

Apache Velocity updated.

EE-8010

The JMS Connector no longer leaks connections and now honors connection pools in XA mode with Solace JMS.

MULE-19848/SE-2228

MUnit no longer fails with a RejectedExecutionException error.

SE-22728

Scheduler runs using cron expressions are no longer rejected if other scheduler components are under back pressure.

SE-22941

This releases fixes an issue that caused a No qualifying bean of type 'org.mule.extensions.java.internal.cache.JavaModuleLoadingCache' available error.

MULE-19896/SE-23142

An issue that caused a No qualifying bean of type 'org.mule.extensions.java.internal.cache.JavaModuleLoadingCache' available error no longer occurs.

MULE-19896/SE-23142

The JMS Connector no longer leaks connections and now honors connection pools in XA mode with Solace JMS.

MULE-19848/SE-22284

HTTP requests with 100-continue are now processed as expected.

MULE-19884/SE-22637

DataWeave

Flow retyping inside dynamic functions now works as expected.

DW-677

DataWeave no longer incorrectly sets autostreaming.

DW-918

The UnsupportedTypeCoercionToLiteralException error is now caught when using the similar operator (~=).

DW-932

JSON streaming now works correctly.

DW-940

The AttributeDelegate function no longer causes a stack overflow error.

SE-23494

Removing objects by property name now works as expected.

SE-23444

When using arrays, the XML writer properly keeps namespaces.

SE-23299

DataWeave now correctly parses large strings in JSON transformations.

SE-23291

A Scatter Gather issue that caused DataWeave to throw the ArrayIndexOutOfBoundsException error no longer occurs.

SE-22431

Comparison operators for dateTime type now work as intended.

SE-22025

Local variable resolution now works as expected.

SE-21847

Avoid closing resources prematurely when using the write function, which affects MUnit tests.

SE-23483

Fix OutOfMemory error using writeLinesWith function, which affected the ndjson module.

SE-23759

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20211222

Description Issue

Mule

The FlowProcessMediator no longer leaks the payload of the first request.

MULE-19869

If the redelivery policy is exhausted in a source configured with transactions, Mule no longer raises an error that runs in a loop.

MULE-19915

Processors in subflows now get the processing strategy of the root flow.

MULE-19924

MUnit tests now initialize object stores inside redelivery policies.

MULE-19928/SE-20765

Autogenerated Mule connectors no longer fail with NumberFormatException errors.

MULE-19871/SE-21463

Applications that implement a VM Listener source no longer raise java.lang.IllegalStateException: No connection has been bound errors and quit.

SE-22172

This releases fixes performance issues with the Web Service Consumer connector when deployed in CloudHub.

SE-22245

You can now redeploy applications that were in a stopped state when they were deleted.

MULE-19890/SE-22261

DataWeave now escapes the \ symbol when used in combination with the " symbol.

MULE-19900/SE-22346

The batch processing On Complete phase no longer fails if it encounters an error stream.

EE-8020/SE-22386

Logs no longer show reconnection successful messages when reconnection attempts to the FTP server are exhausted because the server is unavailable.

SE-22434

Transactions opened by the JMS Listener are no longer rolled back.

MULE-19919/SE-23039

You can now perform parallel deployments of apps that are linked to a domain and share a configuration.

MULE-19912/SE-23123

Mule now recognizes Eclipse Temurin by Adoptium (formerly Adopt OpenJDK project) as a recommended JDK Vendor and no longer raises an INFO-level log message.

MULE-19917/SE-23354

Apache Commons Compress upgraded to version 1.21.

EE-8088

GSON upgraded to version 2.8.9.

EE-8154

When a source is configured to use transactions, and the message ID for the redelivery policy is blank or null, the source no longer fails to find the redelivery attempts counter.

MULE-19921

You can now use the inline string array parameter on operations defined with the Mule XML SDK.

MULE-19853

Kryo updated to version 4.0.2.

EE-8153

Apache Velocity updated.

EE-8010

MUnit no longer fails with a RejectedExecutionException error.

SE-22728

Scheduler runs using cron expressions are no longer rejected if other scheduler components are under back pressure.

SE-22941

An issue that caused a No qualifying bean of type 'org.mule.extensions.java.internal.cache.JavaModuleLoadingCache' available error no longer occurs.

MULE-19896/SE-23142

A performance degradation related to processing parallel requests for applications deployed to the latest Mule runtime version in Runtime Fabric no longer occurs.

EE-8150/SE-23510

The JMS Connector no longer leaks connections and now honors connection pools in XA mode with Solace JMS.

MULE-19848/SE-22284

DataWeave

DataWeave now shows the root cause of an error when an exception occurs while reading an input.

SE-22939

This release resolves an OutOfMemory error when using the writeLinesWith function, which affected the ndjson module.

SE-23759

3.9.5 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 3.9.5-20211224

Description Issue

After upgrading from Mule runtime version 3.8.5 to 3.9.5, the CXF Component no longer raises exceptions in working configurations.

MULE-19889/SE-21182

A ClassNotFoundException: Cannot load class 'scala.None$' exception error no longer occurs with large batch jobs.

EE-8140/SE-21240

You can now redeploy applications that were in a stopped state when they were deleted.

MULE-19890/SE-22261

HTTP requests with 100-continue are now processed as expected.

MULE-19884/SE-22637

Deployment failures no longer repeat Exception locking polling lock errors in the logs.

MULE-19923/SE-22641

A request encoded with double slashes in the URI parameter no longer results in No listener found.

MULE-19933/SE-22967

Mule now recognizes Eclipse Temurin by Adoptium (formerly Adopt OpenJDK project) as a recommended JDK Vendor and no longer raises an INFO-level log message.

MULE-19917/SE-23354

Addressed a regression introduced in November patch 3.9.5-20211018, which caused an Unexpected character error in some Mule applications.

SE-22635

Added new system property mule.setVariable.inheritedMimeType.disable=false. When set to true, Mule checks if the MIME type is set in a set-variable component configuration.

MULE-19941

December 9, 2021

The December 9 patch update for Mule versions 4.4.0 and 4.3.0 addresses a regression in the December 1 patch update. This patch includes all fixes from December 1 as well as the November patch.

The December 9 patch appears as an available runtime version update regardless of whether you installed the December 1 patch. This patch follows the auto-update schedule in the table above.

Fixed Issues

4.4.0 Runtime Updates

Description Issue

Addressed a regression in the initial December patch update.

SE-23349

4.3.0 Runtime Updates

Description Issue

Addressed a regression in the initial December patch update.

SE-23349

December 1, 2021

What’s New

3.8.x, 3.9.x, 4.1.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

Fixed Issues

4.4.0 Runtime Updates

Description Issue

Reverted the fix for SE-17741 (Object Store v2 only) to prevent a race condition with custom TTL (time to live) settings.

SE-23500

4.3.0 Runtime Updates

Description Issue

Reverted the fix for SE-17741 (Object Store v2 only) to prevent a race condition with custom TTL (time to live) settings.

SE-23500

4.2.2 Runtime Updates

Description Issue

Reverted the fix for SE-17741 (Object Store v2 only) to prevent a race condition with custom TTL (time to live) settings.

SE-23500

4.2.1 Runtime Updates

Description Issue

Reverted the fix for SE-17741 (Object Store v2 only) to prevent a race condition with custom TTL (time to live) settings.

SE-23500

November 8, 2021

The November 8 patch update for Mule versions 4.4.0 and 4.3.0 addresses a regression in the November 1 patch update. This patch includes all fixes from November 1.

The November 8 patch appears as an available runtime version update regardless of whether you installed the November 1 patch. This patch follows the auto-update schedule in the table above.

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20211104

Description Issue

QueryParams are no longer lost when HTTP redirects take place.

MULE-19811

Addressed a regression in the initial November patch update.

SE-23349

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20211104

Description Issue

QueryParams are no longer lost when HTTP redirects take place.

MULE-19811

Addressed a regression in the initial November patch update.

SE-23349

November 1, 2021

What’s New

3.8.x, 3.9.x, 4.1.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

  • Updated to the latest operating system security patches.

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0-20211026

Description Issue

Mule

Fixed NullPointerException handling when serializing or transforming Mule errors from the Until Successful component.

MULE-19811

Added missing copyStrategy elements to caching strategy the extension model.

EE-8112

The CachedConnectionProvider no longer returns the same connection to a source if sourceCallback.onConnectionException(e) is called.

MULE-19678

An issue with nesting referenced Flow Reference components no longer occurs.

MULE-19831/SE-22539

Fixed a memory leak in org.mule.runtime.core.internal.rx.FluxSinkRecorder.

MULE-19846/SE-22780

Applications now start correctly after the September patch update is applied.

MULE-19815/SE-22845

Fixed an issue with adding Anypoint Connector for Snowflake (Snowflake Connector) to Studio.

SE-23107

Fixed a scheduling mechanism issue in Anypoint MQ that appeared when the Subscriber operation used the Polling type.

MULE-19843/SE-23031

Fixed an invalid configuration error in custom connectors built with the XML SDK.

MULE-19858/SE-23113

Fixed a memory leak in FlowProcessMediator.

SE-22773

Fixed intermittent No listener errors during Studio deployments or flow restarts.

MULE-19533/SE-21576/SE-20958

Mule now handles concurrent requests correctly when a Mule application makes an HTTP request that returns a 301 redirect.

SE-22922/SE-19944

DataWeave

Fixed a ClassCastException that occurred in the Avro module by correcting its generated MIME type.

SE-21869

Comments within YAML files processed in Mule applications are no longer erased.

DW-706

You can now disable the removal of self-referencing implicit variables.

DW-893

DataWeave now allows mixed content structures (text and nodes) when reading and writing XML content.

SE-21464

Functions in the Dates module now accept one-digit numbers for months and days.

DW-894

Improved the performance of splitting functionality.

DW-776

Improved the performance of the JSON module.

DW-706

Object Store v2

Object Store v2 now correctly displays custom time to live (TTL) values in the Object Store page in Runtime Manager.

SE-17741

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20211026

Description Issue

Mule

The CachedConnectionProvider no longer returns the same connection to a source if sourceCallback.onConnectionException(e) is called.

MULE-19678/SE-21176

Fixed NullPointerException handling when serializing or transforming Mule errors from the Until Successful component.

MULE-19811/SE-20502

Fixed a ClassCastException that occurred in the Avro module by correcting its generated MIME type.

SE-21869

An issue with nesting referenced Flow Reference components no longer occurs.

MULE-19831/SE-22539

Fixed a memory leak in org.mule.runtime.core.internal.rx.FluxSinkRecorder.

MULE-19846/SE-22780

Applications now start correctly after the September patch update is applied.

MULE-19815/SE-22845

Caffeine cache now correctly processes large payloads with a VM queue.

MULE-19869/SE-22773

The Scheduler component no longer causes intermittent deployment failures.

MULE-19774/SE-22851

Mule now handles concurrent requests correctly when a Mule application makes an HTTP request that returns a 301 redirect.

SE-22922/SE-19944

DataWeave

Fixed a ClassCastException that occurred in the Avro module by correcting its generated MIME type.

SE-21869

Object Store v2

Object Store v2 now correctly displays custom time to live (TTL) values in the Object Store page in Runtime Manager.

SE-17741

To prevent deserialization issues, the remove operation now returns null after removing a key value.

SE-21485

4.2.2 Runtime Updates

Description Issue

Object Store v2

Object Store v2 now correctly displays custom time to live (TTL) values in the Object Store page in Runtime Manager.

SE-17741

4.2.1 Runtime Updates

Description Issue

Object Store v2

Object Store v2 now correctly displays custom time to live (TTL) values in the Object Store page in Runtime Manager.

SE-17741

3.9.5 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.5-20211018

Description Issue

Mule

HTTP requests now complete at the end of a Request-Reply scope.

MULE-19780/SE-21042

If you stop a server that is part of a server group, applications using that runtime no longer show a status of undeploying in Runtime Manager.

MULE-19783/SE-21872

When cache is enabled on an application, the MuleSoft Expression Language (MEL) no longer evaluates the NullSafe .? operator to null.

MULE-19785/SE-22515

If you set mule.compoundCorrelationId.disable to true, foreach operations no longer use a different correlationId for every iteration.

MULE-19844/SE-22632

Mule runtime now checks if the MIME type is set in the set-variable configuration.

MULE-19814/SE-22635

October 6, 2021

What’s New

3.8.x, 3.9.x, 4.1.x, 4.2.x, 4.3.0, and 4.4.0 Runtime Updates

Fixed Issues

4.4.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.4.0

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

Improved code compilation. Implicit inputs are not added if a variable with the same name is explicitly defined.

DW-630

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20210915

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

Updated the OkHttp library dependency to version 4.9.1 in Object Store v2.

MQ-2548

4.2.2 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.2.2-20210915

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

4.2.1 Runtime Updates

Description Issue

Updated the OkHttp library dependency to version 4.9.1 in Object Store v2.

MQ-2548

3.9.5 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.5-20210915

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

September 7, 2021

What’s New

3.8.x, 3.9.x, 4.1.x, 4.2.x, and 4.3.0 Runtime Updates

  • Updated to the latest operating system security patches.

Fixed Issues

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20210823

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

A PGP decryption failure no longer occurs in MuleSoft Government Cloud.

4.2.2 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.2.2-20210823

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

3.9.5 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.5-20210823

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.

August 3, 2021

3.8.x, 3.9.x, 4.1.x, 4.2.x, and 4.3.0 Runtime Updates

  • Updated to the latest operating system security patches.

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20210719

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.

4.2.2 Runtime Updates

Issue Description

MQ-2548

Updated the OkHttp library dependency to version 4.9.1 in Object Store v2.

3.9.5 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.5-20210719

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.

July 6, 2021

3.8.x, 3.9.x, 4.1.x, 4.2.x, and 4.3.0 Runtime Updates

  • Updated to the latest operating system security patches.

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20210622

Issue Description

SE-20152

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

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.

4.2.2 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.2.2-20210622

Issue Description

SE-20152

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

4.2.1 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.2.1-20210622

Issue Description

SE-20152

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

3.9.5 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.5-20210622

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.

June 10, 2021

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20210609

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

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

3.8.x, 3.9.x, 4.1.x, 4.2.x, and 4.3.0 Runtime Updates

  • Updated to the latest operating system security patches.

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20210601

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.5-20210517

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 Runtime Updates

  • Updated to the latest operating system security patches.

May 4, 2021

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.

3.8.x, 3.9.x, 4.1.x, and 4.2.x Runtime Updates

  • Updated to the latest operating system security patches.

  • The CloudHub worker volumes are now encrypted.

4.2.2 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.2.2-20210419

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.1.6-20210419

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.5-20210419

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.

3.8.1 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.8.1-20210419

Issue Description

SE-20324/SE-4273

DataWeave: Fixed an issue that caused a seekable stream to produce invalid output.

April 10, 2021

3.8.x and 4.1.x Runtime Updates

Updated to the latest operating system security patches.

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.

3.8.x, 3.9.x, 4.1.x, 4.2.x, and 4.3.0 Runtime Updates

Updated to the latest operating system security patches.

4.3.0 Runtime Updates

MUnit distribution ID that corresponds with these fixes: 4.3.0-20210322

Issue Description

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.2.2-20210322

Issue Description

SE-19858

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

SE-19257

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

SE-19846

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

3.9.5 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.5-20210322

Issue Description

SE-20201

Resolved an Object Store v2 error No partition named that occurred after migrating to Mule version 3.9.5.

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.4-20210322

Issue Description

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.3-20210322

Issue Description

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.8.5 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.8.5-20210322

Issue Description

SE-19950

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

3.8.3 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.8.3-20210322

Issue Description

SE-6424

DataWeave: Fixed an issue to avoid leaking dw-buffer-input*.tmp files.

March 19, 2021

4.3.0 Runtime Updates

Issue Description

SE-20108

Fixed a serialization problem that occurred when using the Cache scope with a persistent Mule object store or Object Store v2.

March 9, 2021

3.8.x, 3.9.x, 4.1.x, 4.2.x, and 4.3.0 Runtime Updates

Updated to the latest operating system security patches.

4.3.0 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.3.0-20210304

Issue Description

SE-19542

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

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.2.2-20210304

Issue Description

SE-19542

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

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.2.1-20210222

Issue Description

SE-19542

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

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.2.0-20210222

Issue Description

SE-19542

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

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.1.6-20210304

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.1.5-20210222

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.5-20210304

Issue Description

SE-19818

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

3.9.4 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.4-20210222

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.3-20210222

Issue Description

SE-19428

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

3.9.2 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.2-20210222

Issue Description

SE-19428

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

3.9.1 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.1-20210222

Issue Description

SE-19428

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

3.9.0 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.0-20210222

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 Runtime Release

MUnit distribution ID that corresponds with these fixes: 3.9.5

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

3.8.4, 3.8.5, 3.8.7, 3.9.0, 3.9.1, 3.9.2, 3.9.3, 3.9.4 Runtime Updates

Updated to the latest operating system security patches.

February 2, 2021

All 3.8.x, 3.9.x, 4.1.x, 4.2.x, and 4.3.0 Runtime Updates

Updated to the latest operating system security patches.

4.3.0 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.3.0-20210119

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

SE-18775

Fixed an issue that caused batch jobs to hang while using persistent queues.

Introduced two new flags:

  • batch.persistent.queue.disable

    Set the value to true to disable the persistent queue for the batch job.

  • batch.persistent.queue.wait.timeout

    Set the value to greater than 500 milliseconds to use long polling for the batch job, which helps resolve the issue.

    By default, the batch job uses short polling.

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.2.2-20210129

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

SE-18775

Fixed an issue that caused batch jobs to hang while using persistent queues.

Introduced two new flags:

  • batch.persistent.queue.disable

    Set the value to true to disable the persistent queue for the batch job.

  • batch.persistent.queue.wait.timeout

    Set the value to greater than 500 milliseconds to use long polling for the batch job, which helps resolve the issue.

    By default, the batch job uses short polling.

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.2.1-20210118

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

SE-18775

Fixed an issue that caused batch jobs to hang while using persistent queues.

Introduced two new flags:

  • batch.persistent.queue.disable

    Set the value to true to disable the persistent queue for the batch job.

  • batch.persistent.queue.wait.timeout

    Set the value to greater than 500 milliseconds to use long polling for the batch job, which helps resolve the issue.

    By default, the batch job uses short polling.

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.2.0-20210120

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

SE-18775

Fixed an issue that caused batch jobs to hang while using persistent queues.

Introduced two new flags:

  • batch.persistent.queue.disable

    Set the value to true to disable the persistent queue for the batch job.

  • batch.persistent.queue.wait.timeout

    Set the value to greater than 500 milliseconds to use long polling for the batch job, which helps resolve the issue.

    By default, the batch job uses short polling.

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.1.6-20210118

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

SE-18775

Fixed an issue that caused batch jobs to hang while using persistent queues.

Introduced two new flags:

  • batch.persistent.queue.disable

    Set the value to true to disable the persistent queue for the batch job.

  • batch.persistent.queue.wait.timeout

    Set the value to greater than 500 milliseconds to use long polling for the batch job, which helps resolve the issue.

    By default, the batch job uses short polling.

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.1.5-20210118

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

SE-18775

Fixed an issue that caused batch jobs to hang while using persistent queues.

Introduced two new flags:

  • batch.persistent.queue.disable

    Set the value to true to disable the persistent queue for the batch job.

  • batch.persistent.queue.wait.timeout

    Set the value to greater than 500 milliseconds to use long polling for the batch job, which helps resolve the issue.

    By default, the batch job uses short polling.

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.1.4-20210120

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

SE-18775

Fixed an issue that caused batch jobs to hang while using persistent queues.

Introduced two new flags:

  • batch.persistent.queue.disable

    Set the value to true to disable the persistent queue for the batch job.

  • batch.persistent.queue.wait.timeout

    Set the value to greater than 500 milliseconds to use long polling for the batch job, which helps resolve the issue.

    By default, the batch job uses short polling.

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.1.3-20210120

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.1.2-20210121

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

SE-18775

Fixed an issue that caused batch jobs to hang while using persistent queues.

Introduced two new flags:

  • batch.persistent.queue.disable

    Set the value to true to disable the persistent queue for the batch job.

  • batch.persistent.queue.wait.timeout

    Set the value to greater than 500 milliseconds to use long polling for the batch job, which helps resolve the issue.

    By default, the batch job uses short polling.

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.

4.1.1 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.1.1-20210121

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

SE-18775

Fixed an issue that caused batch jobs to hang while using persistent queues.

Introduced two new flags:

  • batch.persistent.queue.disable

    Set the value to true to disable the persistent queue for the batch job.

  • batch.persistent.queue.wait.timeout

    Set the value to greater than 500 milliseconds to use long polling for the batch job, which helps resolve the issue.

    By default, the batch job uses short polling.

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

SE-10638

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

SE-12393

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

3.9.4 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.4-20210120

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.3-20210120

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.2-20210120

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

3.9.1 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.1-20210120

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

3.9.0 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.0-20210120

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

SE-7803

DataWeave: Added support for surrogate characters in UTF-8.

3.8.7 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.8.7-20210120

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

3.8.6 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.8.6-20210120

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

3.8.5 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.8.5-20210121

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

SE-8423

DataWeave: Added the system property com.mulesoft.weave.closeAfterFunCall to control if dw function should close stream after call.

SE-7005

DataWeave: Added the system properties com.mulesoft.dw.mapping.cache.size to control mapping cache and com.mulesoft.dw.p_function.cache.size to control p function cache.

SE-18237

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

3.8.4 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.8.4-20210120

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

3.8.3 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.8.3-20210120

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

3.8.2 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.8.2-20210121

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

SE-6424

DataWeave: Fixed an issue to avoid leaking dw-buffer-input*.tmp files.

3.8.1 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.8.1-20210121

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

SE-6424

DataWeave: Fixed an issue to avoid leaking dw-buffer-input*.tmp files.

SE-8423

DataWeave: Added a new system property com.mulesoft.weave.closeAfterFunCall to control if a DataWeave function should close a stream after it is called.

SE-4620

DataWeave: Fixed an issue where files were not being closed.

3.8.0 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.8.0-20210120

Issue Description

SE-14788

Improved troubleshooting information to include Mule EE logs in the CloudHub application logs when an app crashes multiple times in a row

MULE-19140/DW-371

DataWeave: Fixed an issue with property handling.

January 7, 2021

All 3.8.x, 3.9.x, 4.1.x, 4.2.x, and 4.3.0 Runtime Updates

Updated to the latest operating system security patches.

4.3.0 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.3.0-20210105

Issue Description

SE-18354

Fixed an issue with Runtime Manager agent version 2.4.11 in which the web socket reserved a large amount of memory to buffer connections.

SE-17855

Fixed an issue with Object Store v2 that caused Unable to check existence of object with key errors after updating the Mule runtime engine to the last release.

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.2.2-20210105

Issue Description

SE-18354

Fixed an issue with Runtime Manager agent version 2.4.11 in which the web socket reserved a large amount of memory to buffer connections.

SE-17855

Fixed an issue with Object Store v2 that caused Unable to check existence of object with key errors after updating the Mule runtime engine to the last release.

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.2.1-20201130

Issue Description

SE-18354

Fixed an issue with Runtime Manager agent version 2.4.11 in which the web socket reserved a large amount of memory to buffer connections.

SE-17855

Fixed an issue with Object Store v2 that caused Unable to check existence of object with key errors after updating the Mule runtime engine to the last release.

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.2.0-20201201

Issue Description

SE-18354

Fixed an issue with Runtime Manager agent version 2.4.11 in which the web socket reserved a large amount of memory to buffer connections.

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.1.6-20201130

Issue Description

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.1.5-20201130

Issue Description

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.4-20201130

Issue Description

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.2 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.2-20201130

Issue Description

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.9.1-20201130

Issue Description

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.8.7-20201210

Issue Description

SE-18595

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

3.8.4 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.8.4-20201209

Issue Description

SE-5578

Fixed an issue in which spring:import could be used only once in global functions.

SE-18595

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

EE-7569

Updated the Grizzly dependency to version 2.3.36-MULE-019.

December 1, 2020

All 3.8.x, 3.9.x, 4.1.x, 4.2.x, and 4.3.0 Runtime Updates

  • Updated to the latest operating system security patches.

November 3, 2020

All 3.8.x, 3.9.x, 4.1.x, and 4.2.x Runtime Updates

  • Updated to the latest operating system security patches.

4.3.0 Runtime Update

MUnit distribution ID that corresponds with these fixes: 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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 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 8, 2020

4.3.0 Runtime Update

  • Updated to the latest operating system security patches.

October 6, 2020

All 3.8.x, 3.9.x, 4.1.x, and 4.2.x Runtime Updates

  • Updated to the latest operating system security patches.

4.2.2 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.2.2-20200921

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.2.1-20200921

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.1.6-20200921

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.1.5-20200921

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 3.8.7-20200921

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

All 3.8.x, 3.9.x, 4.1.x, 4.2.x, and 4.3.0 Runtime Updates

  • Updated to the latest operating system security patches.

  • Updated to the latest JDK 8 minor version.

4.3.0 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.3.0-20200824

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.

SE-17080

Fixed an error that occurred when sending a request to an app using OAuth2 authentication with Object Store v2.

SE-17119

Fixed an issue that caused deployments to fail for apps using OAuth2 authentication with Object Store v2.

SE-17454

Fixed an issue in which setting the value of expirationInterval to -1 specified a TTL of 0 seconds (rather than the expected unlimited TTL) and caused the object store to expire immediately.

4.2.2 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.2.2-20200824

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.

SE-17080

Fixed an error that occurred when sending a request to an app using OAuth2 authentication with Object Store v2.

SE-17119

Fixed an issue that caused deployments to fail for apps using OAuth2 authentication with Object Store v2.

SE-17454

Fixed an issue in which setting the value of expirationInterval to -1 specified a TTL of 0 seconds (rather than the expected unlimited TTL) and caused the object store to expire immediately.

4.2.1 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.2.1-20200824

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.

SE-17080

Fixed an error that occurred when sending a request to an app using OAuth2 authentication with Object Store v2.

SE-17119

Fixed an issue that caused deployments to fail for apps using OAuth2 authentication with Object Store v2.

SE-17454

Fixed an issue in which setting the value of expirationInterval to -1 specified a TTL of 0 seconds (rather than the expected unlimited TTL) and caused the object store to expire immediately.

4.2.0 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.2.0-20200824

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.1.6-20200824

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 Runtime Update

MUnit distribution ID that corresponds with these fixes: 4.1.5-20200824

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.

3.9.2 Runtime Update

Issue Description

SE-17135

Fixed an issue in which inbound metrics for HTTP-based apps stopped working when auto discovery was enabled.

3.9.1 Runtime Update

Issue Description

SE-17135

Fixed an issue in which inbound metrics for HTTP-based apps stopped working when auto discovery was enabled.

3.9.0 Runtime Update

Issue Description

SE-17135

Fixed an issue in which inbound metrics for HTTP-based apps stopped working when auto discovery was enabled.

3.8.7 Runtime Update

Issue Description

SE-17135

Fixed an issue in which inbound metrics for HTTP-based apps stopped working when auto discovery was enabled.

August 17, 2020

All 3.8.x, 3.9.x, 4.1.x, 4.2.x, and 4.3.0 Runtime Update

  • Updated to the latest operating system security patches (no Mule runtime engine update).

August 4, 2020

4.3.0 Runtime Update

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

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

  • Upgraded the Object Store v2 plugin to version 4.0.27. (SE-13603/SE-10677/SE-16728)

Known Issues

The 4.3.0 release contains the following known issues with Object Store v2:

  • Two known issues when using OAuth2 authentication with an app with an object store:

    When sending a request to the app, the following error occurs: (SE-17080)

    {"error_description":"Invalid credentials","error":"invalid_client"}%

    When deploying the app, deployment fails with the following error: (SE-17119)

    Partition with name _defaultPersistentObjectStore does not exist in store

    To work around these issues, use the following clientStore configuration:

    <oauth2-provider:config
    	name="Oauth2_Provider_Config" doc:name="Oauth2 Provider Config"
    	doc:id="fbb2f727-5e7d-4cf5-8a84-52de678a017a" providerName="Mulesoft"
    	clientSecurityProvider="${myCompany.oauth.clientSecurityProvider}"
    	supportedGrantTypes="${myCompany.oauth.grantType}"
    	listenerConfig="api-httpListenerConfig" clientStore="Object_store">
  • A known issue with setting the TTL (time to live) value for an object store (SE-17454):

    Setting the value of entryTtl to 0 and the value of expirationInterval to less than or equal to 0 configures the TTL as 0 seconds (rather than the expected unlimited TTL). This behavior causes the object store entries to expire immediately and any operations that are dependent on the key in the app to fail.

    To work around this issue, remove the entryTtl and entryTtlUnit properties from the object store definition.

4.2.2 Runtime Update

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

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

  • Upgraded the Object Store v2 plugin to version 4.0.27. (SE-13603/SE-10677/SE-16728)

Known Issues

The 4.2.2 release contains the following known issues with Object Store v2:

  • Two known issues when using OAuth2 authentication with an app with an object store:

    When sending a request to the app, the following error occurs: (SE-17080)

    {"error_description":"Invalid credentials","error":"invalid_client"}%

    When deploying the app, deployment fails with the following error: (SE-17119)

    Partition with name _defaultPersistentObjectStore does not exist in store

    To work around these issues, use the following clientStore configuration:

    <oauth2-provider:config
    	name="Oauth2_Provider_Config" doc:name="Oauth2 Provider Config"
    	doc:id="fbb2f727-5e7d-4cf5-8a84-52de678a017a" providerName="Mulesoft"
    	clientSecurityProvider="${myCompany.oauth.clientSecurityProvider}"
    	supportedGrantTypes="${myCompany.oauth.grantType}"
    	listenerConfig="api-httpListenerConfig" clientStore="Object_store">
  • A known issue with setting the TTL (time to live) value for an object store (SE-17454):

    Setting the value of entryTtl to 0 and the value of expirationInterval to less than or equal to 0 configures the TTL as 0 seconds (rather than the expected unlimited TTL). This behavior causes the object store entries to expire immediately and any operations that are dependent on the key in the app to fail.

    To work around this issue, remove the entryTtl and entryTtlUnit properties from the object store definition.

4.2.1 Runtime Update

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

  • Fixed an issue in which an Object Store v2 exception appeared in the deployment log when starting applications that did not have Use Object Store v2 enabled. (SE-16728)

  • Upgraded the Object Store v2 plugin to version 4.0.27. (SE-13603/SE-10677/SE-16728)

Known Issues

The 4.2.1 release contains the following known issues with Object Store v2:

  • Two known issues when using OAuth2 authentication with an app with an object store:

    When sending a request to the app, the following error occurs: (SE-17080)

    {"error_description":"Invalid credentials","error":"invalid_client"}%

    When deploying the app, deployment fails with the following error: (SE-17119)

    Partition with name _defaultPersistentObjectStore does not exist in store

    To work around these issues, use the following clientStore configuration:

    <oauth2-provider:config
    	name="Oauth2_Provider_Config" doc:name="Oauth2 Provider Config"
    	doc:id="fbb2f727-5e7d-4cf5-8a84-52de678a017a" providerName="Mulesoft"
    	clientSecurityProvider="${myCompany.oauth.clientSecurityProvider}"
    	supportedGrantTypes="${myCompany.oauth.grantType}"
    	listenerConfig="api-httpListenerConfig" clientStore="Object_store">
  • A known issue with setting the TTL (time to live) value for an object store (SE-17454):

    Setting the value of entryTtl to 0 and the value of expirationInterval to less than or equal to 0 configures the TTL as 0 seconds (rather than the expected unlimited TTL). This behavior causes the object store entries to expire immediately and any operations that are dependent on the key in the app to fail.

    To work around this issue, remove the entryTtl and entryTtlUnit properties from the object store definition.

4.2.0 Runtime Update

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

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

3.9.4 Runtime Update

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

3.9.3 Runtime Update

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

3.9.2 Runtime Update

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

3.9.1 Runtime Update

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

3.9.0 Runtime Update

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

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

3.8.7 Runtime Update

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

All 3.8.x, 3.9.x, 4.1.x, and 4.2.x Runtime Updates

  • Updated to the latest operating system security patches.

July 13, 2020

4.2.2 Runtime Update

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates in CloudHub Mule 4.x runtimes. (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)

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

  • Updated to the latest operating system security patches.

4.2.1 Runtime Update

  • Upgraded Object Store v2 plugin to 4.0.25.

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates in CloudHub Mule 4.x runtimes. (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)

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

  • Updated to the latest operating system security patches.

Known Issue

The 4.2.1 release contains one known issue. (SE-16728)

The following Object Store v2 exception appears in the deployment log when starting applications that do not have Use Object Store v2 enabled:

Listener 'com.mulesoft.objectstore.cloud.internal.CloudObjectStoreListenerService' failed to process notification 'onArtifactCreated'

You can safely ignore the error. It has no impact on functionality.

July 9, 2020

4.3.0 Runtime Update

  • 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 serialization problem with policies using the 'Rate limit SLA' 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)

  • Updated to the latest operating system security patches.

4.2.0 Runtime Update

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates in CloudHub Mule 4.x runtimes. (AGW-4199)

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

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

  • Updated to the latest operating system security patches.

4.1.6 Runtime Update

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates in CloudHub Mule 4.x runtimes. (AGW-4199)

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

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

  • Updated to the latest operating system security patches.

4.1.5 Runtime Update

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates in CloudHub Mule 4.x runtimes. (AGW-4199)

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

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

  • Updated to the latest operating system security patches.

4.1.4 Runtime Update

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates in CloudHub Mule 4.x runtimes. (AGW-4199)

  • Updated to the latest operating system security patches.

4.1.3 Runtime Update

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates in CloudHub Mule 4.x runtimes. (AGW-4199)

  • Updated to the latest operating system security patches.

4.1.2 Runtime Update

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates in CloudHub Mule 4.x runtimes. (AGW-4199)

  • Updated to the latest operating system security patches.

3.9.4 Runtime Update

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

  • Updated to the latest operating system security patches.

3.9.1 Runtime Update

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

  • Updated to the latest operating system security patches.

June 11, 2020

4.2.2 Runtime Update:

  • Security update.

June 9, 2020

4.2.x, 4.1.6, and 4.1.5 Runtime Updates:

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

June 2, 2020

4.3.0 Runtime Update:

  • Mule application threw the wrong HTTP response status code when api-gateway:autodiscovery was enabled. (SE-15935)

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

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

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

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

  • When an HTTP Listener is source of the flow, trying to reference a flow variable from the flow’s error response builder, the variable could not be found if a source policy was applied to the Listener. (MULE-18378)

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

  • Fixed an issue that might rarely cause a key collision with the ManagedCursorProvider cache. (MULE-18370)

  • MULE:OVERLOAD exception is thrown when first policy contains a Cache scope and second policy contains a Try scope error-handler. (MULE-18369)

  • Fixed a problem that prevented an application from starting after stopping using Runtime Manager. (MULE-18364)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • Fixed ObjectStoreToMapAdapter thrown exceptions when used or accessed concurrently. (MULE-18172)

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

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

  • Fixed an issue in which the Scheduler incorrectly ran twice. (SE-13691)

4.2.2 Runtime Update:

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

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

  • Resolved a problem with semantic versioning build-metadata when deploying an application. (SE-11087)

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

  • Fixed an issue where an exception affected class loading, even though the class exists in the dependencies using shared libraries. (SE-14245)

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

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

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

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

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

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

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

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

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

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

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

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

4.2.1 Runtime Update:

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

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

4.2.0 Runtime Update:

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

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

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

  • Resolved an unexpected state with the error handler org.mule.runtime.core.internal.event.EventContextDeepNestingException. (SE-15597)

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

4.1.6 Runtime Update:

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

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

4.1.5 Runtime Update:

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

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

3.9.3 Runtime Update:

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

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

3.8.4 Runtime Update:

  • Fixed an java.util.concurrent.TimeoutException: Poll timeout expired issue when processing HTTP incoming application requests. (SE-13504)

All 3.8.x, 3.9.x, 4.1.x, and 4.2.x Runtime Update:

  • Updated to the latest operating system security patches.

May 5, 2020

4.3.0 Runtime Update:

  • Fixed an overload error that occurred when an API had a combination of two policies using caching and error-handler components. (MULE-18369)

All 3.8.x, 3.9.x, 4.1.x, and 4.2.x Runtime Update:

  • Updated to the latest operating system security patches.

April 20, 2020

4.2.x Runtime Update:

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

April 14, 2020

4.2.x Runtime Update:

  • Fixed an issue that, under high concurrency, might cause a leak in HTTP requests due to a race condition scenario. (SE-15540)

April 11, 2020

3.8.5 Runtime Update:

  • Fixed an issue with the RAML parser referencing other files using !include. (SE-15625)

April 10, 2020

4.2.1 Runtime Update:

  • Fixed a regression problem in Object Store v2 that was introduced with the April 7 update.

April 9, 2020

4.2.2 Runtime Update:

  • Fixed a regression problem in Object Store v2 that was introduced with the April 7 update.

April 7, 2020

All 4.x, 3.9.x, and 3.8.x Runtime Updates:

  • Set a new MetaspaceSize default to 128M so that it is possible to increase the metaspace memory and go beyond a more conservative threshold. This change is also introduced to maintain consistency with on-premises distributions.

  • Fixed issues to ensure RAML parser compatibility.

  • Targeted security fix.

April 4, 2020

4.2.2 Runtime Update:

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

April 2, 2020

4.2.1 Runtime Update:

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

  • Fixed an issue that affected the Web Service Consumer, causing long WSDL parsing times with multiple levels of nested imports. (SE-13634)

  • Fixed the error Failed to read geo directoryjava.nio.file.NoSuchFileException that appeared after deploying an application. (SE-14946)

March 30, 2020

4.2.2 Runtime Update:

  • Fixed an issue that caused StackOverflow errors in applications using the Database connector under heavy load. (SE-14663)

  • Fixed the error Failed to read geo directoryjava.nio.file.NoSuchFileException that appeared after deploying an application. (SE-14946)

March 29, 2020

All 3.8.x, 3.9.x, and 4.1.x Runtime Updates:

  • Fixed an issue with the RAML Parser.

  • Fixed the error Failed to read geo directoryjava.nio.file.NoSuchFileException that appeared after deploying an application. (SE-14946)

March 27, 2020

4.2.2 Runtime Update:

  • Updated the mule-http-ee-service dependency to version 1.5.3.

  • Fixed an OutOfMemory issue that occurred when Database Connector did not properly release heap memory when the request timed out. (SE-13982)

  • Fixed an issue in which an HTTP Request using NTLM authentication did not send the request payload resulting in a timeout request operation. (SE-13547)

March 25, 2020

4.2.1 Runtime Update:

  • Improved Object Store v2 initialization on CloudHub.

  • Improved usage of Object Store v2 by internal Mule 4 components.

  • Added support for fixed TTL in Object Store v2.

  • Fixed an issue in which an HTTP Request using NTLM authentication did not send the request payload resulting in a timeout request operation. (SE-13547)

  • Fixed an issue that caused FlowStack : <empty> log messages with invalid expressions. (SE-13660)

March 18, 2020

All 3.8.x, 3.9.x, and 4.x Runtime Update:

  • Security fixes

3.9.0, 3.9.1, 3.9.2, and 3.9.3 Runtime Update:

  • Improved Object Store v2 initialization by Mule runtime engine.

March 16, 2020

4.2.2 Runtime Update:

  • Fixed an issue that caused empty FlowStack log messages.

  • Fixed an issue that occurred when the Scatter-Gather component contained Flow References.

  • Fixed an issue that affected the OAuth token refresh.

March 12, 2020

3.9.4 Runtime Update:

  • Fixed an issue that affected listener reconnection in the WMQ Connector.

  • Fixed an issue with DataWeave memory management. (SE-14927)

  • Improved Object Store v2 initialization by Mule runtime engine.

March 9, 2020

4.1.2, 4.1.3, 4.1.4, and 4.2.0 Runtime Update:

  • Reduced log levels for API gateway recoverable errors. (AGW-3949)

4.1.3, 4.1.4, 4.1.5, 4.1.6, 4.2.0, 4.2.1, and 4.2.2 Runtime Update:

  • Fixed an issue that caused unexpected behavior after a policy threw an unhandled exception during deployment.

4.2.0, 4.2.1, and 4.2.2 Runtime Update:

  • Fixed an issue in which an HTTP Request using NTLM authentication did not send the request payload resulting in a timeout request operation. (SE-13547)

4.2.0 and 4.2.2 Runtime Update:

  • Fixed an issue that affected the Web Service Consumer, causing long WSDL parsing times with multiple levels of nested imports. (SE-13634)

4.1.4 Runtime Update:

  • Fixed an issue in which a DataWeave expression used to display information with the Logger component failed in high-load scenarios. (SE-10706)

3.8.6 Runtime Update:

  • Fixed an issue that caused validation errors in the API console.

March 6, 2020

3.8.7 Runtime Update:

  • Fixed an issue that caused thread-related exceptions.

March 3, 2020

4.1.2 and 4.1.5 Runtime Update:

  • Fixed a policy violation issue that was introduced with the previous runtime version update.

3.8.2 and 3.8.7 Runtime Update:

  • Improved Object Store v2 initialization by Mule runtime engine.

February 27, 2020

4.1.2 Runtime Update:

  • Fixed an issue that caused unexpected behavior after a policy threw an unhandled exception during deployment.

  • Fixed an issue that resulted in a FileNotFoundException error while executing a DataWeave expression in large-batch scenarios, which was caused by prematurely closing the content stream. (SE-9379)

3.8.3, 3.8.5, and 3.8.6 Runtime Update:

  • Improved Object Store v2 initialization by Mule runtime engine.

February 26, 2020

3.8.0 and 3.8.1 Runtime Update:

  • Improved Object Store v2 initialization by Mule runtime engine.

February 20, 2020

4.2.0, 4.2.1, and 4.2.2 Runtime Update:

  • Fixed an issue in which batch records didn’t process when the Persistent queues option was enabled. (SE-13300)

4.1.5, 4.1.6, 4.2.1, and 4.2.2 Runtime Update:

  • Reduced log levels for API Gateway recoverable errors. (AGW-3949)

4.2.0 Runtime Update:

  • Fixed inconsistent DataWeave transformations called via a SOAP router when executed across Linux and Windows operating systems. [SE-11664]

3.9.4 Runtime Update:

  • Added a system property to avoid removing the object store folder on disposal. (SE-14361)

3.9.3 and 3.9.4 Runtime Update:

  • Monitoring enhancements

February 14, 2020

4.1.5, 4.1.6, 4.2.1, and 4.2.2 Runtime Update:

  • Added support for HTTP header injection in Anypoint Connector for HTTP. (MULE-17706)

4.2.1 Runtime Update:

  • Fixed an issue in which the refresh dance did not execute after the access token expired. (MULE-17812)

3.9.1 and 3.9.2 Runtime Update:

  • Fixed an issue in which special characters were corrupt in the Content-Disposition header. (SE-13575)

3.8.7 Runtime Update:

  • Added a system property to avoid removing the object store folder on disposal. (SE-14361)

February 13, 2020

4.1.5, 4.1.6, 4.2.1, and 4.2.2 Runtime Update:

  • Monitoring enhancements

4.2.2 Runtime Update:

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

  • Fixed dw::core::Strings::substringAfterLast function not working as expected. (SE-14808)

February 11, 2020

3.9.4 Runtime Update:

  • Fixed an issue with the RAML console and API proxies. (SE-13029)

  • Fixed an issue with OAuth authentication. (MULE-17688)

  • Fixed issues with DataWeave transformations. (SE-14020, SE-14371, SE-14423)

4.2.1 and 4.2.2 Runtime Update:

  • Fixed an issue in which the refresh dance did not execute after the access token expired. (MULE-17812)

  • Fixed an issue in which Mule apps did not process more than one message from Anypoint MQ. (SE-14595)

4.2.2 Runtime Update:

  • The toBase64 and fromBase64 functions now behave the same way as in version 4.2.1. (SE-14606)

  • DataWeave fixes for union and enum types in Avro schemas. (SE-14561 and SE-14625)

February 10, 2020

4.1.1, 4.1.2, 4.1.3, 4.1.4, 4.1.5, and 4.1.6 Runtime Update:

  • Security fixes

February 4, 2020

3.8.7, 3.9.0, 3.9.1, 3.9.2, 3.9.3, and 3.9.4 Runtime Update:

  • Security fixes

3.9.0 Runtime Update:

  • Improved Object Store v2 initialization by Mule runtime engine.

February 3, 2020

4.2.0, 4.2.1, and 4.2.2 Runtime Update:

  • Security fixes

January 22, 2020

3.8.7 Runtime Update:

  • Reverted the January 10 patch that addressed SE-5737.

January 10, 2020

4.2.2 Runtime Update:

  • Updated with latest OS security patches.

3.8.0, 3.8.1, 3.8.2, 3.8.3, 3.8.4, 3.8.5, 3.8.6, 3.8.7, 3.9.0, 3.9.1, 3.9.2, 4.1.1, 4.1.2, 4.1.3, 4.1.4, 4.1.5, 4.1.6, 4.2.0, and 4.2.1 Runtime Update:

  • Fixed an issue where AdoptJdk was shown as an unsupported vendor.

  • Updated with latest OS security patches.

3.9.3 and 3.9.4 Runtime Update:

  • Fix an issue where special characters were corrupted in the Content-Disposition header fileName attribute. (SE-14283)

  • Fixed an issue where AdoptJdk was shown as an unsupported vendor.

  • Updated with latest OS security patches.

3.8.7 Runtime Update:

  • Fixed an issue where illegal access to an event from a non-corresponding thread resulted in a java.lang.IllegalStateException: Only owner thread can write to message error. (SE-5737)

3.8.4 Runtime Update:

  • Improved Object Store v2 initialization by Mule runtime engine.

January 9, 2020

4.2.1 and 4.2.2 Runtime Update:

  • Fixed an issue where the API gateway was using the Business Group organization ID instead of the Master organization ID for OAuth provider operations. (SE-13786)

December 24, 2019

3.8.4 and 3.8.6 Runtime Update:

  • CloudHub Mule worker-reliability enhancements and performance improvements

December 16, 2019

4.2.1 Runtime Update:

  • Fixed a DataWeave OOM error Direct buffer memory in 0.1 worker. (SE-13951)

December 13, 2019

4.2.2 Runtime Update:

  • Fixed a DataWeave OOM error Direct buffer memory in 0.1 worker. (SE-13951)

3.9.3 Runtime Update:

  • Fixed an issue in which special characters were corrupt in the Content-Disposition header. (SE-13575)

December 12, 2019

3.9.3 and 3.9.4 Runtime Update:

  • Fixed an issue where Anypoint Monitoring didn’t show inbound metrics. (SE-13726)

  • Fixed an issue where the Anypoint Monitoring agent was blocking threads. (SE-14121)

December 10, 2019

3.8.0, 3.8.1, 3.8.2, 3.8.3, 3.8.4, 3.8.5, 3.8.6, 3.8.7, 3.9.0, 3.9.1, 3.9.2, 3.9.3, 3.9.4, 4.1.1, 4.1.2, 4.1.3, 4.1.4, 4.1.5, 4.1.6, 4.2.0, 4.2.1, and 4.2.2 Runtime Update:

  • Updated with latest OS and security patches.

3.8.5 Runtime Update:

  • Fixed an issue where the API console for CloudHub applications generated RAML parsing errors. [SE-13887]

  • Fixed an issue where the Mule monitor failed to recover an unresponsive Mule process. [SE-14096]

4.2.1 Runtime Update:

  • Fixed an issue that caused a MULE:FLOW_BACK_PRESSURE error in 4.2.x. [SE-13832]

  • Fixed an Out of Memory issue in Batch Aggregator. [SE-13440]

4.2.0 Runtime Update:

  • Fixed an issue that caused a MULE:FLOW_BACK_PRESSURE error in 4.2.x. [SE-13832]

3.9.3 Runtime Update:

  • Fixed an issue in which special characters were corrupt in the Content-Disposition header. (SE-13575)

December 4, 2019

3.8.6 Runtime Update:

  • Fixed an issue where the Mule monitor failed to recover an unresponsive Mule process. [SE-14096]

December 2, 2019

3.9.3 Runtime Update:

  • Fixed an issue where API Kit failed to validate yyyy-m-d and yyyy-m-dThh:mi:ss date formats. [SE-12947]

  • Fixed an issue where the monitoring feature didn’t work on workers with a static IP address. [SE-13729]

November 29, 2019

4.2.1 and 4.2.0 Runtime Update:

  • Fixed an issue where the configuration property output not correct when the prefix was escaped. [SE-13196]

3.9.1 Runtime Update:

  • Fixed an issue where the monitoring feature didn’t work on workers with a static IP address. [SE-13729]

November 25, 2019

4.1.6 and 4.2.1 Runtime Update:

  • Fixed an issue where the monitoring feature didn’t work on workers with a static IP address. [SE-13729]

November 21, 2019

4.1.5 Runtime Update:

  • Fixed a NullPointerException that occurred with patch SE-12807-4.2.1-1.0 applied. [SE-13580]

  • Fixed an issue where the monitoring feature didn’t work on workers with a static IP address. [SE-13729]

4.2.0 Runtime Update:

  • Performance assessment for WS consumer when using explicit custom-transport-configuration [SE-10687]

  • Fixed an issue where the monitoring feature didn’t work on workers with a static IP address. [SE-13729]

November 14, 2019

3.9.2 Runtime Update:

  • Fixed an issue where the monitoring feature didn’t work on workers with a static IP address. [SE-13729]

November 12, 2019

4.2.1 Runtime Update:

  • Flow backpressure check is now performed before source policies are applied. [MULE-16513]

November 7, 2019

3.9.3 Runtime Update:

  • RAML console now works on CloudHub proxy. [SE-13029]

November 6, 2019

3.8.6, 3.8.7, 3.9.0, 3.9.1, 3.9.2, 3.9.3, 4.1.2, 4.1.3, 4.1.4, 4.1.5, 4.1.6, 4.2.0, and 4.2.1 Runtime Update:

  • Fixed an issue with persistent queues in the Europe control plane [SE-13657]

  • Fixed a backward-compatibility issue with TLS support. [SE-13613]

October 31, 2019

4.1.6 Runtime Update:

  • Fixed the KryoException (Could not deserialize object) error [SE-13124]

4.1.5 Runtime Update:

  • Fixed an issue in which overriding encrypted properties failed when referenced from within a properties file in datasource definition [SE-13494]

  • Fixed the KryoException (Could not deserialize object) error [SE-13124]

October 30, 2019

4.2.1 Runtime Update:

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

  • Fixed an issue in which Mule request was not being processed intermittently, even though the request was received by the Listener [SE-13677]

  • Fixed an issue with the splitBy function failing with the error Caused by: java.io.IOException: Stream is closed when running without debugging mode [SE-12836]

  • Fixed error HTTP Packet header is too large [SE-13213]

  • Added the port where HTTP listens to logs [SE-13099]

  • Fixed an issue where the ListenerConfig attribute of <oauth2-provider:config> was not working when referencing domain project listener [SE-11990]

  • Fixed an issue with filenames in UTF-8 where the £ character in a multipar/form-data was transformed to £ in ASCII [SE-9292]

  • Fixed an issue that caused a NullPointerException error with patch SE-12807-4.2.1-1.0 applied [SE-13580]

  • Fixed an issue where Try Scope with On Error Continue stops and does not continue processing [SE-13184]

  • Fixed an issue with configuration property values that include special characters [SE-13196]

4.2.0 Runtime Update:

  • Fixed an issue in which Mule request was not being processed intermittently, even though the request was received by the Listener [SE-13677]

  • Fixed an issue with the splitBy function failing with the error Caused by: java.io.IOException: Stream is closed when running without debugging mode [SE-12836]

  • Fixed an issue that caused a NullPointerException error with patch SE-12807-4.2.1-1.0 applied [SE-13580]

  • Fixed an issue with configuration property values that include special characters [SE-13196]

  • Fixed a JMS connector configuration error [SE-11912]

October 24, 2019

3.9.0, 3.9.1 and 3.8.7 Runtime Update:

  • Fixed the org.glassfish.grizzly.connectionpool.Endpoint.connect and java.lang.AbstractMethodError errors with the 3.9.1 patch release (10-22-2019). [SE-13669]

3.8.7 Runtime Update:

  • Fixed an issue when insecure TLS TrustStore was used, the patch release SE-12252 caused NoSuchMethodError exception error in CloudHub, which prevented applications from being deployed. [SE-13615]

October 23, 2019

4.2.1 and 4.2.0 Runtime Update:

  • Fixed an issue that caused Mule runtime engine to throw exception java.lang.NoSuchMethodError: org.mule.runtime.extension.api.runtime.config.ConfigurationStats.getRunningSources(). [SE-13611]

October 22, 2019

4.2.1 Runtime Update:

  • Fixed an issue where a CloudHub patch release caused an error: [SE-13612]

    java.lang.NoSuchMethodError: org.mule.runtime.core.internal.util.rx.ConditionalExecutorServiceDecorator.<init>(Lorg/mule/runtime/api/scheduler/Scheduler;Ljava/util/function/Predicate;)V

3.9.x Runtime Updates:

  • Fixed java.util.concurrent.TimeoutException: Poll timeout expired issue. [SE-13504]

  • Fixed an issue when insecure TLS TrustStore was used, the patch release SE-12252 caused NoSuchMethodError exception error in CloudHub, which prevented applications from being deployed. [SE-13615]

October 16, 2019

4.2.1 Runtime Update:

  • Fixed an issue where the HTTP request did not renegotiate NTLM authentication when new credentials were provided [SE-11204]

  • Fixed a leak in the first classloader that invokes an HTTP service in the Mule app. [EE-6968]

4.2.0 Runtime Update:

  • Fixed an issue where the JWT policy was not responding under load when the CPU_INTENSIVE operation was present in the application. [SE-13091]

  • SFTP Connector now reconnects after a JSchException error. [SE-12626]

  • Fixed an issue where the CloudHub worker was unresponsive and unable to start on its own. [SE-13004]

  • Fixed an issue with excessive logging filling /tmp and partition 100%. [SE-12896]

  • Fixed 100% CPU usage issue due to HTS service. [SE-13388]

  • Fixed inconsistent property loading. [SE-13118]

  • Fixed an issue where the HTTP request did not renegotiate NTLM authentication when new credentials were provided [SE-11204]

  • Fixed a leak in the first classloader that invokes an HTTP service in the Mule app. [EE-6968]

4.1.5 Runtime Update:

  • HTTP Request Connector was not honoring the queryParameter order. [SE-11445]

  • SFTP Connector was not reconnecting after JSchException error. [SE-12626]

  • Fixed an issue where the CloudHub worker was unresponsive and unable to start on its own. [SE-13004]

  • Fixed an issue with excessive logging filling /tmp and partition 100%. [SE-12896]

  • Fixed 100% CPU usage issue due to HTS service. [SE-13388]

  • Fixed inconsistent property loading. [SE-13118]

4.1.2, 4.1.3 and 4.1.4 Runtime Updates:

  • SFTP connector was not reconnecting after JSchException error. [SE-12626]

  • Fixed an issue where the CloudHub worker was unresponsive and unable to start on its own. [SE-13004]

  • Fixed an issue with excessive logging filling /tmp and partition 100%. [SE-12896]

  • Fixed 100% CPU usage issue due to HTS service. [SE-13388]

  • Fixed inconsistent property loading. [SE-13118]

3.9.1 and 3.8.7 Runtime Updates:

  • Fixed an issue where the CloudHub worker was unresponsive and unable to start on its own. [SE-13004]

  • Fixed an issue with excessive logging filling /tmp and partition 100%. [SE-12896]

  • Fixed 100% CPU usage issue due to HTS service. [SE-13388]

  • Fixed inconsistent property loading. [SE-13118]

3.9.3 Runtime Updates:

  • Fixed an issue with CloudHub Mule runtime engine 3.9.3 AMI using an evaluation license. [SE-13525]

October 15, 2019

4.2.1 Runtime Update:

  • Fixed an issue where the JWT policy was not responding under load when the CPU_INTENSIVE operation was present in the application. [SE-13091]

  • Inbound metrics did not appear for some apps. [SE-13095]

  • Fixed an issue where the CloudHub worker was unresponsive and unable to start on its own. [SE-13004]

  • Fixed an issue with excessive logging filling /tmp and partition 100%. [SE-12896]

  • Fixed 100% CPU usage issue due to HTS service. [SE-13388]

  • Fixed inconsistent property loading. [SE-13118]

  • SFTP connector was not reconnecting after JSchException error. [SE-12626]

4.1.6 Runtime Update:

  • Inbound metrics did not appear for some apps. [SE-13095]

  • Fixed an issue where the CloudHub worker was unresponsive and unable to start on its own. [SE-13004]

  • Fixed an issue with excessive logging filling /tmp and partition 100%. [SE-12896]

  • Fixed an issue where the HTS service was not deleting file descriptors. [SE-13388]

  • Fixed inconsistent property loading. [SE-13118]

  • SFTP connector was not reconnecting after JSchException error. [SE-12626]

October 9, 2019

3.9.3 Runtime Updates:

  • Inbound metrics do not appear for some apps. [SE-13095]

September 20, 2019

4.1.6 Runtime Update:

  • Mule app encounters deadlock when submitting parallel requests in CloudHub. [SE-13047]

  • Fixed memory leak on PolicyStateHandler for error scenarios. [SE-12906]

4.1.5 Runtime Update:

  • FTPS connector is not reusing connection from the pool. [SE-12776]

  • A nonexistent file path causes SFTP "Connection pool is exhausted" error. [SE-12279]

4.1.4 and 4.2.0 Runtime Updates:

  • A nonexistent file path causes SFTP "Connection pool is exhausted" error. [SE-12279]

3.9.0, 3.9.1, 3.9.2, and 3.9.3 Runtime Update:

  • Update CloudHub AMI with new version of July 2019 security patch. [SE-13138]

September 16, 2019

3.8.7 Runtime Update:

  • CloudHub Mule worker-reliability enhancements and performance improvements

September 9, 2019

4.1.5 Runtime Update:

  • Deadlock when submitting parallel requests. [SE-13047]

  • Inbound metrics do not appear for app. [SE-13095]

  • Fix memory leak on PolicyStateHandler for error scenarios [SE-12906]

3.9.3, 4.1.1, 4.1.2, 4.1.3, 4.1.5, and 4.2.0 Runtime Update:

  • Inbound metrics do not appear for app. [SE-13095]

September 5, 2019

4.2.0 Runtime Update:

  • Sinks must be used by only one thread when running a transaction. [MULE-16936]

3.9.0 Runtime Update:

  • APIKit incorrectly overrides the default transformation graph. [SE-7162]

All 3.8.x Runtime Updates:

  • If defaultCipherSuites isn’t specified, all cipher suites supported by enabled protocols are used. [SE-12252]

September 4, 2019

All 4.2.x Runtime Updates:

  • CloudHub Mule worker-reliability enhancements and performance improvements for 1 vCore

  • CloudHub Mule workers now include Correlation ID in log messages.

All 4.1.x Runtime Updates:

  • CloudHub Mule worker-reliability enhancements and performance improvements for 1 vCore

  • CloudHub Mule workers now include Correlation ID in log messages.

All 3.9.x Runtime Updates:

  • CloudHub Mule worker-reliability enhancements and performance improvements for 1 vCore

September 3, 2019

4.2.1 Runtime Update:

  • SFTP with public key authentication fails after 5 minutes. [SE-11329]

  • SFTP listener with identity file and start delay set as 0 fails to retrieve file. [SE-11198]

  • CloudHub Mule worker-reliability enhancements and performance improvements for 0.2 vCore

4.2.0 Runtime Update:

  • High CPU when using VM listener with persistent queue even when the app is idle. [SE-11994]

  • SFTP with public key authentication fails after 5 minutes. [SE-11329]

  • SFTP listener with identity file and start delay set to 0 fails to retrieve file. [SE-11198]

  • CloudHub Mule worker-reliability enhancements and performance improvements for 0.2 vCore

All 4.1.x Runtime Updates:

  • CloudHub Mule worker-reliability enhancements and performance improvements for 0.2 vCore

All 3.9.x Runtime Updates:

  • CloudHub Mule worker-reliability enhancements and performance improvements for 0.2 vCore

August 30, 2019

4.2.1 Runtime Update:

  • Anypoint Visualizer is not showing inbound connections. [SE-12476]

  • Inbound Metrics are missing for app in Anypoint Monitoring. [SE-12832]

  • High CPU - When using VM listener with persistent queue even when the app is idle. [SE-11994]

3.8.7, 3.9.3, and 4.1.5 Runtime Update:

  • Anypoint Visualizer is not showing inbound connections. [SE-12476]

  • Inbound Metrics are missing for app in Anypoint Monitoring. [SE-12832]

August 28, 2019

4.2.1 Runtime Update:

  • Address incomplete fix for SE-12772.

4.2.0 Runtime Update:

  • Try scope with transactions forces all components to execute on CPU_LITE threads. [SE-12772]

  • Cannot open a new cursor on a closed stream inside a Foreach scope. [SE-12807]

August 27, 2019

4.2.1 Runtime Update:

  • Try scope with transactions forces all components to execute on CPU_LITE threads. [SE-12772]

  • Cannot open a new cursor on a closed stream inside a for-each scope. [SE-12807]

  • SFTP connection pool is exhausted when file path does not exist. [SE-12279]

  • Resolved a problem in which the Cache scope fails validation when the payload is empty when entering the scope. [SE-12743]

4.1.5 Runtime Update:

  • Try scope with transactions forces all components to execute on CPU_LITE threads. [SE-12772]

  • Cannot open a new cursor on a closed stream inside a for-each scope. [SE-12807]

4.1.4 Runtime Update:

  • Try scope with transactions forces all components to execute on CPU_LITE threads. [SE-12772]

All 3.9.x Runtime Updates:

  • CloudHub Mule worker-reliability enhancements and performance improvements for 0.1 vCore

August 23, 2019

4.2.0 and 4.2.1 Runtime Update:

  • CloudHub Mule worker-reliability enhancements and performance improvements for 0.1 vCore

August 22, 2019

4.1.1, 4.1.2, 4.1.3, 4.1.4, and 4.1.5 Runtime Update:

  • CloudHub Mule worker-reliability enhancements and performance improvements for 0.1 vCore

August 14, 2019

3.9.0 Runtime Update:

  • NoSuchMethodError on APIKit after latest update [SE-12795]

3.8.7 Runtime Update:

  • Add new Visualizer and Monitoring capabilities

  • Fix Threat Protection Policies showing internal class names when an invalid XML or JSON payload are sent. [SE-12389]

3.8.6 Runtime Update:

  • Fix Threat Protection Policies showing internal class names when an invalid XML or JSON payload are sent. [SE-12389]

3.8.5 Runtime Update:

  • Fix Threat Protection Policies showing internal class names when an invalid XML or JSON payload are sent. [SE-12389]

August 9, 2019

3.9.3 Runtime Update:

  • Empty X-MULE-DDOS-VIOLATION header reaching backend. [SE-12611]

August 8, 2019

4.2.0 and 4.2.1 Runtime Update:

  • Out of Memory in Metaspace when redeploying application. [SE-10506]

  • Spring dependency collision between runtime and connectors. [SE-12204]

  • Flow Backpressure error when running DataWeave transformation. [SE-12583]

  • Extensions configuration being leaked over time. [SE-12495]

  • Update OSv2 plugin to version 4.0.22 using POST method instead of PUT for store requests. [SE-11308]

  • OAuth Module for HTTP Requester is leaking threads. [SE-12028]

  • Unlabelled endpoint is shown within the Monitoring dashboard. [SE-12397]

4.1.5 Runtime Update:

  • IllegalStateException on batch job with concurrency. [SE-12451]

August 7, 2019

4.1.5 Runtime Update:

  • Fixed inconsistent DataWeave transformations called via a SOAP router when executed across Linux and Windows operating systems. [SE-11664]

  • Strings with special characters are not being logged correctly. [SE-12345]

  • Out of Memory in Metaspace when redeploying application. [SE-10506]

  • Extensions configuration being leaked over time. [SE-12495]

  • Update OSv2 plugin to version 4.0.22 using POST method instead of PUT for store requests. [SE-11308]

  • OAuth Module for HTTP Requester is leaking threads. [SE-12028]

  • Unlabelled endpoint is shown within the Monitoring dashboard. [SE-12397]

4.1.4 Runtime Update:

  • OAuth Module for HTTP Requester is leaking threads. [SE-12028]

  • Fix scheduling issue when using OAuth2 policies. [SE-10874]

  • Unlabelled endpoint is shown within the Monitoring dashboard. [SE-12397]

3.9.3, 3.9.2 Runtime Updates:

  • Maximum attribute size limit exceeded when parsing XML using Object to XML transformer. [SE-11752]

  • Maximum attribute size limit exceeded when parsing XML using DataWeave. [SE-11914]

All 3.9.x Runtime Updates:

  • Fix Threat Protection Policies showing internal class names when an invalid XML or JSON payload are sent. [SE-12389]

  • SSL cipher suites list changed with latest patch of 3.9.0 and 3.9.1 in CloudHub. [SE-12252]

  • Analytics collector does not allow to access the message. [SE-12446]

July 16, 2019

4.2.0 Runtime Update:

  • IllegalStateException on batch job with concurrency. [SE-12451]

  • Faster application deployment with Monitoring feature disabled.

4.1.5 Runtime Update:

  • Faster application deployment with Monitoring feature disabled.

3.9.3 Runtime Update:

  • Fix Policies that manage client applications not working as expected when encryption is configured.

  • Faster application deployment with Monitoring feature disabled.

July 12, 2019

3.9.2 and 3.9.3 Runtime Update:

  • Address incomplete fix for SE-11195 (Error loading System Properties).

July 11, 2019

4.2.0 Runtime Update:

  • PipelineMessageNotificationListener returns a PipelineMessageNotification with null event when an exception is raised in the Mule flow. [MULE-17081]

  • org.springframework.beans.factory.support.NullBean cannot be cast. [SE-12247]

  • FlowRef component inside an on-error scope causes duplicate chain execution. [SE-12017]

3.9.2 and 3.9.3 Runtime Update:

  • Error loading System Properties. [SE-11195]

June 27, 2019

4.2.0 Runtime Update:

  • Update scheduler pool configuration in design environment.

3.8.7, 3.8.6, 3.8.5, 3.8.4, 3.8.2, 3.8.1 and 3.8. Runtime Update:

  • Switched from OracleJDK 8 to OpenJDK 8.

June 26, 2019

4.1.5 Runtime Update:

  • IBM MQ listener receiving REPLY_TO queue header message unable to reconnect after the queue manager restarts. [SE-11261]

June 19, 2019

4.1.5 Runtime Update:

  • Improved memory consumption in Monitoring data path

June 12, 2019

4.2.0, 4.1.5, 4.1.4, 4.1.3, 4.1.2 and 4.1.1 Runtime Update:

  • NullPointerException when running Mule applications with batches and persistent queues enabled in CloudHub. [SE-11599]

June 7, 2019

4.1.5 Runtime Update:

  • Batch job corrupted when debugging app [SE-9826]

3.9.1 and 3.9.2 Runtime Update:

  • JSON validation fails with the error: error: object instance has properties which are not allowed by the schema: [SE-11753]

June 5, 2019

4.1.5, 4.1.4, 4.1.3, 4.1.2 and 4.1.1 Runtime Update:

  • Switched from OracleJDK 8 to OpenJDK 8

June 4, 2019

4.1.4, 4.1.5 and 4.2.0 Runtime Update:

  • Fix custom policies reusing class loader between versions. [SE-12023]

  • Fix class loading isolation issues when initializing apps. [SE-11887]

4.1.1, 4.1.2, 4.1.3, 4.1.4 and 4.1.5 Runtime Update:

  • Fix policy violations not being sent when caused by an automated policy.

May 28, 2019

4.2.0 Runtime Update:

  • APIKit validation error issue after version 1.1.9 [SE-11839]

  • Sporadic NullPointerException in Grizzly ClientHttpResponseImpl.getProcessingState() [SE-8085]

  • Accept-Expression in Batch job not evaluated correctly [SE-11666]

  • JMS consumer stops consuming messages after the stop/start flow operation [SE-11450]

  • Removed unexpected warnings and errors related to file system permissions in logs when using secure properties [SE-7975]

4.1.5 Runtime Update:

  • Sporadic NullPointerException in Grizzly ClientHttpResponseImpl.getProcessingState() [SE-8085]

  • Accept-Expression in Batch job not evaluated correctly [SE-11666]

  • JMS consumer stops consuming messages after the stop/start flow operation [SE-11450]

3.9.2, 3.9.1 and 3.9.0 Runtime Update:

  • Removed unexpected warnings and errors related to file system permissions in logs when using secure properties [SE-7975]

May 24, 2019

4.1.5 and 4.2.0 Runtime Update:

  • Visualizer properties not picked up from the mule-app.properties file [SE-10374]

3.9.2 Runtime Update:

  • Address incomplete fix in OAuth service [SE-10423]

  • Visualizer properties not picked up from the mule-app.properties file [SE-10374]

3.9.1 Runtime Update:

  • Address incomplete fix in OAuth service [SE-10423]

  • Thread leak after redeployment when using OAuth client credentials [SE-10217]

May 22, 2019

3.9.2 Runtime Update:

  • Switched from OracleJDK 8 to OpenJDK 8

  • Address incomplete fix in RAML parser [SE-11926]

3.9.1 Runtime Update:

  • Switched from OracleJDK 8 to OpenJDK 8

  • Address incomplete fix in RAML parser [SE-11926]

3.9.0 Runtime Update:

  • Switched from OracleJDK 8 to OpenJDK 8

May 21, 2019

3.9.1 Runtime Update:

  • Address incomplete fix in RAML parser [SE-10737]

May 16, 2019

3.8.7 Runtime Update:

  • FTP connector not closing connections properly when server closes the socket. [SE-11688]

May 14, 2019

4.2.0 Runtime Update:

  • Persistent queues not working for batch and vm:publish-consume operation. [SE-11698, SE-11599, SE-10583]

4.1.1, 4.1.2, 4.1.3, 4.1.4 and 4.1.5 Runtimes Update:

  • Persistent queues not working for batch and vm:publish-consume operation. [SE-11698, SE-11599, SE-10583]

May 8, 2019

4.2.0 Runtime Update:

  • Streaming a large payload through HTTP generates a timeout [SE-10129]

May 2, 2019

4.2.0 Initial Release:

  • Mule 4.2 runs on CloudHub using AdoptOpenJDK 1.8 instead of Oracle JDK.

  • There is an important update included for the API Caching Policy. See the HTTP Caching Release Notes for more information.

  • For information about changes and improvements in the Mule 4.2.0 runtime, see Mule Runtime 4.2.0 Release Notes.

April 26, 2019

4.1.2-4.1.4 Runtime Update:

  • Fix NullPointerException reported in the logs by some connectors when the Monitoring feature is enabled. [SE-11483]

3.9.2 Runtime Update:

  • Address incomplete fix in RAML parser [SE-10737]

  • Ping flow flooding Insight when metadata is enabled and auto restart is set for CloudHub applications [SE-11327]

3.9.1 Runtime Update:

  • Address incomplete fix in RAML parser [SE-10737]

  • Ping flow flooding Insight when metadata is enabled and auto restart is set for CloudHub applications [SE-11327]

3.9.0 Runtime Update:

  • Fix NullPointerException reported in the logs by some connectors when the Monitoring feature is enabled. [SE-11483]

  • Some inbound request failures are not taken into account in Monitoring dashboards. [SE-10544]

  • Visualizer properties are not picked up from the mule-app.properties file. [SE-10374]

  • Ping flow flooding Insight when metadata is enabled and auto restart is set for CloudHub applications [SE-11327]

April 25, 2019

4.1.5 Runtime Update:

  • HTTP Listener discloses full URL in error response. [SE-10302]

  • Fix NullPointerException reported in the logs by some connectors when the Monitoring feature is enabled. [SE-11483]

3.9.2 Runtime Update:

  • RAML with date-only/datetime-only fails to parse in APIKit. [SE-10737]

  • String interpolation in logger component fails on debug mode. [SE-11094]

  • Login screen in API Console disappears. [SE-8445]

  • Fix NullPointerException reported in the logs by some connectors when the Monitoring feature is enabled. [SE-11483]

  • Some inbound request failures are not taken into account in Monitoring dashboards. [SE-10544]

  • Visualizer properties are not picked up from the mule-app.properties file. [SE-10374]

3.9.1 Runtime Update:

  • RAML with date-only/datetime-only fails to parse in APIKit. [SE-10737]

  • String interpolation in logger component fails on debug mode. [SE-11094]

  • Login screen in API Console disappears. [SE-8445]

  • Fix NullPointerException reported in the logs by some connectors when the Monitoring feature is enabled. [SE-11483]

  • Some inbound request failures are not taken into account in Monitoring dashboards. [SE-10544]

  • Visualizer properties are not picked up from the mule-app.properties file. [SE-10374]

April 8, 2019

4.1.5 Runtime Update:

  • Unclosed stream causes memory leak in foreach loop [SE-11390]

  • Degraded performance when using a Custom Transport Configuration in Web Service Consumer [SE-10687]

  • Fixed an issue that resulted in a FileNotFoundException error while executing a DataWeave expression in large-batch scenarios, which was caused by prematurely closing the content stream. (SE-9379)

  • Fixed an issue in which a DataWeave expression used to display information via the Logger component failed on high load scenarios. [SE-10706]

3.9.2 Runtime Update:

  • MEL variable returns null instead of actual value [SE-11479]

3.9.1 Runtime Update:

  • MEL variable returns null instead of actual value [SE-11479]

3.9.0 Runtime Update:

  • Both Visualizer and Monitoring functionality are now controlled through the Anypoint Monitoring UI. After you upgrade to this runtime, your apps no longer appear in Visualizer. The apps are still there, but you need to re-enable Visualizer functionality in the Anypoint Monitoring Settings to see them. For more information, see Enable Monitoring for Mule Apps Deployed to CloudHub.

April 5, 2019

3.9.1 Runtime Update:

  • Both Visualizer and Monitoring functionality are now controlled through the Anypoint Monitoring UI. After you upgrade to this runtime, your apps no longer appear in Visualizer. The apps are still there, but you need to re-enable Visualizer functionality in the Anypoint Monitoring Settings to see them. For more information, see Enable Monitoring for Mule Apps Deployed to CloudHub.

April 4, 2019

3.9.2 Runtime Update:

  • Both Visualizer and Monitoring functionality are now controlled through the Anypoint Monitoring UI. After you upgrade to this runtime, your apps no longer appear in Visualizer. The apps are still there, but you need to re-enable Visualizer functionality in the Anypoint Monitoring Settings to see them. For more information, see Enable Monitoring for Mule Apps Deployed to CloudHub.

March 26, 2019

3.8.7 Runtime Update:

  • SFTP connector is not closing connections [SE-10977]

  • Throttling policy doesn’t clean its cache [SE-10534]

3.8.6 Runtime Update:

  • Throttling policy doesn’t clean its cache [SE-10534]

3.8.4 Runtime Update:

  • Added alerting in case disk usage exceeds threshold [SE-11147]

March 25, 2019

3.9.2 Runtime Update:

  • Oracle type with CLOB field raises error [SE-10726]

  • Database connector file descriptor leaks when processing large payloads [SE-11071]

  • SFTP connector is not closing connections [SE-10977]

  • Throttling policy doesn’t clean its cache [SE-10534]

3.9.1 Runtime Update:

  • Oracle type with CLOB field raises error [SE-10726]

  • Database connector file descriptor leaks when processing large payloads [SE-11071]

March 22, 2019

4.1.1, 4.1.2, 4.1.3, 4.1.4 and 4.1.5 Runtimes Update:

  • Visualizer and Monitoring functionality are part of these CloudHub runtimes now, so there is no need to use separate 4.1.x-AM runtimes any longer.

  • Both Visualizer and Monitoring functionality are now controlled through the Anypoint Monitoring UI. After you upgrade to Mule 4.1.x you will no longer see your apps in Visualizer. They are still there, but you need to re-enable Visualizer functionality in the Anypoint Monitoring Settings. For more information, see enable the Anypoint Monitoring agent.

This release contains the following known issue:

SE-11007: Do not enable advanced app log functionality on 0.1 VCore configurations.

Workaround: Use 0.2 VCore or higher configurations.

March 21, 2019

3.8.4 Runtime Update:

  • Max buffer size fix for file system full [SE-11147]

March 15, 2019

3.9.1 Runtime Update:

  • Schedules not registered [SE-11264]

March 8, 2019

3.8.7 Runtime Update:

  • Dnsmasq unavailable [SE-11197]

3.8.6 Runtime Update:

  • Dnsmasq unavailable [SE-11197]

3.8.5 Runtime Update:

  • Dnsmasq unavailable [SE-11197]

March 7, 2019

4.1.5 Runtime Update:

  • Batch fails in CloudHub with persistent queues enabled [SE-10583]

4.1.4 Runtime Update:

  • Batch fails in CloudHub with persistent queues enabled [SE-10583]

March 6, 2019

4.1.5 Runtime Update:

  • Incorrect handling of backslashes in logger component [SE-10940]

  • NullPointerException when MUnit tries to dispose of object after test [SE-10038]

4.1.4 Runtime Update:

  • NullPointerException when MUnit tries to dispose of object after test [SE-10038]

3.9.2 Runtime Update:

  • Partitioned object store does not delete partition folder [SE-10999]

  • Hung thread in WMQ transport with synchronous processing strategy [SE-10743]

3.9.1 Runtime Update:

  • Hung thread in WMQ transport with synchronous processing strategy [SE-10743]

3.8.7 Runtime Update:

  • Partitioned object store does not delete partition folder [SE-10999]

  • Memory leak in XsltTransformer [SE-8522]

3.8.6 Runtime Update:

  • Partitioned object store does not delete partition folder [SE-10999]

  • Memory leak in XsltTransformer [SE-8522]

3.8.5 Runtime Update:

  • Cache not being cleaned in throttling policy [SE-10534]

February 27, 2019

4.1.5 Runtime Update:

  • Context does not contain key error shown in the logs [SE-10867]

4.1.4 Runtime Update:

  • Context does not contain key error shown in the logs [SE-10867]

February 26, 2019

3.9.2 Runtime Update:

  • Detect Mule unresponsiveness through ping flow

3.9.1 Runtime Update:

  • Detect Mule unresponsiveness through ping flow

3.9.0 Runtime Update:

  • Detect Mule unresponsiveness through ping flow

February 15, 2019

3.9.1 Runtime Update:

  • Include Anypoint Monitoring Agent Extension

3.9.0 Runtime Update:

  • Include Anypoint Monitoring Agent Extension

February 14, 2019

4.1.5 Runtime Update:

  • Address incomplete fix of performance degradation caused by high volume of logging [SE-10742]

February 7, 2019

4.1.5 Runtime Update:

  • ThreadLocal configuration causes performance degradation [SE-10742]

  • Salesforce Marketing connector throws token expired exception [SE-10343]

4.1.4 Runtime Update:

  • Salesforce Marketing connector throws token expired exception [SE-10343]

February 2, 2019

4.1.5 Runtime Update:

  • Gatekeeper policy causes memory leak on policy engine [SE-10641]

4.1.4 Runtime Update:

  • Gatekeeper policy causes memory leak on policy engine [SE-10641]

February 1, 2019

3.9.2 Runtime Update:

  • Include Anypoint Monitoring Agent Extension

January 25, 2019

3.9.2 Runtime Update:

  • ObjectDoesNotExistException on OAuth module [SE-10423]

  • XSD schemas being loaded multiple times cause delayed startup [SE-10529]

3.9.1 Runtime Update:

  • ObjectDoesNotExistException on OAuth module [SE-10423]

  • XSD schemas being loaded multiple times cause delayed startup [SE-10529]

January 24, 2019

4.1.5 Runtime Update:

  • DataWeave distinct operation runs out of memory with a large collection [SE-10548]

  • High CPU usage on DataWeave transformation causes the worker to stop processing [SE-10638]

4.1.4 Runtime Update:

  • DataWeave distinct operation runs out of memory with a large collection [SE-10548]

  • High CPU usage on DataWeave transformation causes the worker to stop processing [SE-10638]

January 2, 2019

4.1.5 Runtime Update:

  • Source error callback is not called when an error is caught in error handler [SE-10212]

4.1.4 Runtime Update:

  • Source error callback is not called when an error is caught in error handler [SE-10212]

3.9.2 Runtime Update:

  • WMQ transport with synchronous processing strategy is not reconnecting [SE-10362]

3.9.1 Runtime Update:

  • WMQ transport with synchronous processing strategy is not reconnecting [SE-10362]

3.9.0 Runtime Update:

  • WMQ transport with synchronous processing strategy is not reconnecting [SE-10362]

December 18, 2018

4.1.5 Runtime Update:

  • ProcessingStrategy internal bufferSize is always 256 for flow-ref [SE-10226]

  • IdempotentRedeliveryPolicy blocks CPU_LITE thread [SE-10306]

4.1.4 Runtime Update:

  • ProcessingStrategy internal bufferSize is always 256 for flow-ref [SE-10226]

  • IdempotentRedeliveryPolicy blocks CPU_LITE thread [SE-10306]

December 13, 2018

3.9.2 Runtime Update:

  • Diagnostic logs download [SE-10249]

3.9.1 Runtime Update:

  • Diagnostic logs download [SE-10249]

3.9.0 Runtime Update:

  • Diagnostic logs download [SE-10249]

December 12, 2018

4.1.4 Runtime Update:

  • Diagnostic logs download [SE-10249]

4.1.3 Runtime Update:

  • Diagnostic logs download [SE-10249]

4.1.2 Runtime Update:

  • Diagnostic logs download [SE-10249]

4.1.1 Runtime Update:

  • Diagnostic logs download [SE-10249]

4.1.0 Runtime Update:

  • Diagnostic logs download [SE-10249]

December 10, 2018

3.9.2 Runtime Update:

  • MEL expression failure with concurrent requests [SE-10166]

3.9.1 Runtime Update:

  • MEL expression failure with concurrent requests [SE-10166]

  • OAuth provider does not honor expired token TTL [SE-8650]

  • LIST command is not issued after reconnection in FTP transport [SE-9323]

  • APIKit validation error doesn’t display the field name [SE-8727]

3.9.0 Runtime Update:

  • OAuth provider does not honor expired token TTL [SE-8650]

  • LIST command is not issued after reconnection in FTP transport [SE-9323]

December 7, 2018

4.1.4 Runtime Update:

  • Invalid XML generated for artifact declaration [MULE-15835]

4.1.3 Runtime Update:

  • Invalid XML generated for artifact declaration [MULE-15835]

December 6, 2018

3.9.2 Runtime Update:

  • Wrapper working directory [SE-10173]

  • Security enhancements

3.9.1 Runtime Update:

  • Wrapper working directory [SE-10173]

  • Security enhancements

3.9.0 Runtime Update:

  • Wrapper working directory [SE-10173]

  • Security enhancements

December 5, 2018

4.1.4 Runtime Update:

  • Batch persistent queue initialization [SE-9688]

  • Wrapper working directory [SE-10173]

  • Expose mule deployment error [SE-8554, SE-9209]

  • Security enhancements

4.1.3 Runtime Update:

  • Batch persistent queue initialization [SE-9688]

  • Wrapper working directory [SE-10173]

  • Expose mule deployment error [SE-8554, SE-9209]

  • Security enhancements

4.1.2 Runtime Update:

  • Batch persistent queue initialization [SE-9688]

  • Wrapper working directory [SE-10173]

  • Security enhancements

4.1.1 Runtime Update:

  • Batch persistent queue initialization [SE-9688]

  • Wrapper working directory [SE-10173]

  • Security enhancements

4.1.0 Runtime Update:

  • Batch persistent queue initialization [SE-9688]

  • Wrapper working directory [SE-10173]

  • Security enhancements

November 26, 2018

4.1.4 Runtime Update:

  • Amazon SQS connector shutdown exception. [SE-9149]

  • Backpressure is not triggered by a saturated CPU_INTENSIVE thread pool. [SE-10078]

4.1.3 Runtime Update:

  • Amazon SQS connector shutdown exception. [SE-9149]

November 22, 2018

4.1.4 Runtime Update:

  • 'Could not deserialize object' in cache component. [SE-9879]

  • DataWeave stream closed intermittently in a batch process. [SE-9974]

  • DataWeave flatten() function is not streaming. [SE-10077]

November 10, 2018

4.1.4 Runtime Update:

  • Invalid Session ID on SFDC connector reconnnection attempt. [SE-9471]

4.1.3 Runtime Update:

  • Invalid Session ID on SFDC connector reconnnection attempt. [SE-9471]

November 9, 2018

4.1.4 Runtime Update:

  • DataWeave stream is closed before being consumed in batch aggregator [SE-9836]

  • Batch process not doing "on complete" step when results collection is empty [SE-9899]

3.9.1 Runtime Update:

  • Addressed deployment issue when using the IMAP reconnection strategy. [SE-9544]

3.9.0 Runtime Update:

  • Response encoding is replaced in Web Service Consumer. [SE-9298]

November 5, 2018

3.9.0 Runtime Update:

  • Let customer fix invalid cron schedules after start [SE-8632]

  • Internal HTTP client enhancements

  • Security enhancements

3.9.1 Runtime Update:

  • Let customer fix invalid cron schedules after start [SE-8632]

  • Internal HTTP client enhancements

  • Security enhancements

November 2, 2018

4.0.0 Runtime Update:

  • License update [SE-9564]

  • Expose mule deployment error [SE-8554, SE-9209]

  • Security enhancements

4.1.0 Runtime Update:

  • License update [SE-9564]

  • Expose mule deployment error [SE-8554, SE-9209]

  • Security enhancements

4.1.1 Runtime Update:

  • License update [SE-9564]

  • Expose mule deployment error [SE-8554, SE-9209]

  • Security enhancements

4.1.2 Runtime Update:

  • License update [SE-9564]

  • Expose mule deployment error [SE-8554, SE-9209]

  • Security enhancements

October 30, 2018

3.8.5 Runtime Update:

  • Payload expression transform error [SE-9452]

October 29, 2018

4.1.4 Runtime Update:

  • Cron schedulers were not properly registered [SE-9861]

October 26, 2018

4.1.4 Runtime Update:

  • Event instances were kept too long in the buffer [SE-9556]

  • Expose mule deployment error [SE-8554, SE-9209]

3.9.1 Runtime Update:

  • NullPointerException while refreshing access token in OAuth with Client Credentials [SE-9613]

  • Response encoding being replaced in Web Service Consumer [SE-9298]

  • Payload expression transform error [SE-9452]

  • Expose mule deployment error [SE-8554, SE-9209]

3.9.0 Runtime Update:

  • Attachment order not being honored in multipart-form-data request [SE-7595]

  • Expose mule deployment error [SE-8554, SE-9209]

3.8.5 Runtime Update:

  • Attachment order not being honored in multipart-form-data request [SE-7595]

  • Transformation graph incorrectly overridden [SE-7162]

October 9, 2018

4.1.3 Runtime Update:

  • Object Store V2 plugin update fixing the encoding of keys when deleting causing not found issue [SE-9505]

  • Batch crashes with ArrayList of HashMap as input [SE-9437]

  • SDK scopes process internal chains as blocking [SE-9315]

  • Cannot open a new cursor on a closed stream using batch processing [SE-9472]

  • DataWeave buffer output FileNotFoundException [SE-9379]

  • Failure to process subflow with async scopes [SE-9395]

October 5, 2018

3.9.1 Runtime update:

  • Updated Object Store v2 plugin version to fix exception not being thrown as the Mule ObjectStore contract specifies. [SE-9551]

3.9.0 Runtime update:

  • Updated Object Store v2 plugin version to fix exception not being thrown as the Mule ObjectStore contract specifies. [SE-9551]

3.8.7 Runtime update:

  • Updated Object Store v2 plugin version to fix exception not being thrown as the Mule ObjectStore contract specifies. [SE-9551]

3.8.6 Runtime update:

  • Updated Object Store v2 plugin version to fix exception not being thrown as the Mule ObjectStore contract specifies. [SE-9551]

3.8.5 Runtime update:

  • Updated Object Store v2 plugin version to fix exception not being thrown as Mule the ObjectStore contract specifies ,[SE-9551]

September 21, 2018

4.1.2 Runtime update:

  • Client Enforcement Policy throwing "No value present" error [SE-8736]

4.1.1 Runtime update:

  • Change token expiration log level from ERROR to WARN [SE-8613]

  • Client Enforcement Policy throwing "No value present" error [SE-8736]

3.9.1 Runtime update:

  • OAuth2 provider not working when offline; support RestClient reconnection [SE-9455]

  • RAML parser uncaught exception [SE-9228]

  • API console RAML validatioan errors [SE-8773]

September 17, 2018

4.1.3 Runtime Update:

  • DW2 lookup function blocks CPU intensive threads [SE-9104]

  • Ability to send "Base64 Encoded client_id and client_secret" in Authorization header for authorization-code-grant-type [SE-9065]

  • Unknown error on Object Store operation [SE-9285]

3.9.1, 4.1.2, 4.1.3 Runtime Updates:

  • Error related to Application Visualizer seen in multiple applications in CloudHub [SE-9143]

August 23, 2018

All 3.8.x, 3.9.x and 4.1.x Runtime Updates:

  • A kernel-level patch to the operating system against the SegmentSmack vulnerability (CVE-2018-5390)

August 14, 2018

4.1.3 Runtime Update:

  • Cache locks CPU lite threads under load. Addressed incomplete fix. [SE-8937]

4.1.2 Runtime Update:

  • Cache locks CPU lite threads under load. Addressed incomplete fix. [SE-8937]

  • SFTP connector not closing connections [SE-8996]

4.1.1 Runtime Update:

  • Cache locks CPU lite threads under load. Addressed incomplete fix. [SE-8937]

  • SFTP connector not closing connections [SE-8996]

July 31, 2018

3.8.7 Runtime Update:

  • Update object store plugin to provide better reconnection strategy on socket timeout exception

3.8.6 Runtime Update:

  • Update object store plugin to provide better reconnection strategy on socket timeout exception

3.8.5 Runtime Update:

  • Update object store plugin to provide better reconnection strategy on socket timeout exception

3.9.1 Runtime Update:

  • StackOverflow on Exception in non-blocking flow [SE-7797]

  • Update object store plugin to provide better reconnection strategy on socket timeout exception

  • Fix Anypoint Visualizer enablement for cached instances

3.9.0 Runtime Update:

  • Infinite loop in non-blocking flow using Scatter Gather [SE-8351]

  • Update object store plugin to provide better reconnection strategy on socket timeout exception

July 30, 2018

4.1.2 Runtime Update:

  • Cache locks CPU lite threads under load [SE-8937]

  • Update object store plugin to provide better reconnection strategy on socket timeout exception

  • Fix Anypoint Visualizer enablement for cached instances

4.1.1 Runtime Update:

  • Cache locks CPU lite threads under load [SE-8937]

  • Update object store plugin to provide better reconnection strategy on socket timeout exception

July 23, 2018

4.1.2 Runtime Update:

  • MuleModuleLoader keeps reference to a BindingContext [SE-8526]

July 18, 2018

4.1.2 Runtime Update:

  • StackOverflow error is non-descriptive [SE-8686]

  • Web Service Consumer ignores CDATA tag in Consume operation [SE-8643]

July 12, 2018

4.1.2 Runtime Update:

  • Implemented retry strategy for Object Store v2 REST client to improve resiliency.

4.1.1 Runtime Update:

  • Implemented retry strategy for Object Store v2 REST client to improve resiliency.

4.1.0 Runtime Update:

  • Implemented retry strategy for Object Store v2 REST client to improve resiliency.

3.9.1 Runtime Update:

  • Implemented retry strategy for Object Store v2 REST client to improve resiliency.

3.9.0 Runtime Update:

  • Implemented retry strategy for Object Store v2 REST client to improve resiliency.

3.8.7 Runtime Update:

  • Implemented retry strategy for Object Store v2 REST client to improve resiliency.

3.8.6 Runtime Update:

  • Implemented retry strategy for Object Store v2 REST client to improve resiliency.

3.8.5 Runtime Update:

  • Implemented retry strategy for Object Store v2 REST client to improve resiliency.

July 10, 2018

4.1.0 Runtime Update:

  • LogAppender instances not cleaned up on redeploy [MULE-15169]

4.1.1 Runtime Update:

  • LogAppender instances not cleaned up on redeploy [MULE-15169]

  • Flow designer deployment fails with HTTP request default header configuration [SE-8088]

  • Batch schema validation failure triggers Serialization Exception [SE-8687]

4.1.2 Runtime Update:

  • LogAppender instances not cleaned up on redeploy [MULE-15169]

  • Flow designer deployment fails with HTTP request default header configuration [SE-8088]

  • Batch schema validation failure triggers Serialization Exception [SE-8687]

  • Mule runtimes versions 3.9.1 and 4.1.2 support Anypoint Visualizer.

  • The 3.9.1-visualizer and 4.1.2-visualizer versions of Mule runtime are deprecated. Use the 3.9.1 and 4.1.2 versions instead.

July 3, 2018

3.8.7 Runtime Update:

  • Fixes NullPointerException in Grizzly ClientHttpResponseImpl.getProcessingState() [SE-8085]

4.1.2 Runtime Update:

  • Fixes DataWeave flatfile transformation returns empty payload [SE-8608]

  • Fixes DefaultEventContext not cleaned up [SE-8526]

June 30, 2018

  • Mule runtime version 3.9.1-visualizer and 4.1.2-visualizer for CloudHub have been released. These runtimes must be used for the application and its dependencies to viewed in Anypoint Visualizer.

June 29, 2018

All 3.8.x, 3.9.x and 4.1.x Runtimes:

  • Adds 256mb SWAP drive for 0.1vCores to address rare scenarios of Native OS out of memory [SE-7207]

  • Fixes an issue where extra properties are injected when monitoring process restarts mule [SE-8590]

All 4.1.x Runtimes:

  • NPE on application startup with specific configuration [MULE-15141]

  • Fixes deployment of an specific application using a system property [MULE-15167]

  • Upgrade Agent to 2.1.3

3.8.4 Runtime Update:

  • Fixes leak on the CXF component (org.apache.cxf.endpoint.ClientImpl) [SE-6455,SE-8107]

3.9.0 Runtime Update:

  • BufferUnderflowException in DataWeave tranformation [SE-7263]

3.9.1 Runtime Update:

  • Fixes leak on the CXF component (org.apache.cxf.endpoint.ClientImpl) [SE-8107]

June 18, 2018

3.9.0 Runtime Update comes with the following fixes:

  • Backoff scheduler log line is always present [SE-8290]

3.9.1 Runtime Update comes with the following fixes:

  • Backoff scheduler log line is always present [SE-8290]

June 6, 2018

3.9.0 Runtime Update comes with the following fixes:

  • Address partial fix for SE-7615 [SE-8370]

  • Metadata replay empties the payload [SE-7081]

  • DW buffer files not being deleted when calling dw() from MEL on large payloads [SE-8423]

3.9.1 Runtime Update comes with the following fixes:

  • Performance degradation with empty MessageProcessorNotificationListener [MULE-14901]

  • DW buffer files not being deleted when calling dw() from MEL on large payloads [SE-8423]

4.1.2 Runtime Update comes with the following fixes:

  • Performance degradation with empty MessageProcessorNotificationListener [MULE-14901]

  • Unable to invoke a service using a WSDL with nested imports [SE-8362]

May 21, 2018

3.9.1 Runtime Update comes with the following fixes:

  • Flow-ref response time increasing over time [SE-8100]

3.9.0 Runtime Update comes with the following fixes:

  • Flow-ref response time increasing over time [SE-8100]

3.8.6 Runtime Update comes with the following fixes:

  • Flow-ref response time increasing over time [SE-8100]

May 11, 2018

3.9.0 Runtime Update comes with the following enhancement:

  • Data Weave does not consider DST +-1H change when converting UTC time stamp to local time stamp [SE-8039]

  • AbstractDbMessageProcessor is leaking connections [SE-7982]

  • BufferUnderflowException on Dataweave transformations [SE-7263]

  • SFTP Password is not masked when special character(^) is used

May 7, 2018

3.8.6 Runtime Update comes with the following enhancement:

  • Data Weave does not consider DST +-1H change when converting UTC time stamp to local time stamp [SE-8039]

  • AbstractDbMessageProcessor is leaking connections [SE-7982]

  • BufferUnderflowException on Dataweave transformations [SE-7263]

April 5, 2018

3.9.0 Runtime Update comes with the following enhancement:

  • Updated the Object Store V2 plugin to provide better error messages

April 4, 2018

3.8.3 Runtime Update comes with the following fixes:

  • Cross-site scripting (reflected) [SE-7930]

  • Mime Type Dissapears when under load [SE-7807]

3.8.4 Runtime Update comes with the following fixes:

  • Cross-site scripting (reflected) [SE-7930]

March 30, 2018

3.8.5 Runtime Update comes with the following fixes:

  • Automatic retry on remote Closed exception does not respect RFC 7320 [SE-7116]

  • SFTP Reconnect throws "Already in lifecycle phase" as a error message [SE-6658]

  • Cross-site scripting (reflected) [SE-7930]

  • Warning logs are emitted when using secured properties [SE-7445]

March 29, 2018

3.8.6 Runtime Update comes with the following fixes:

  • Mime Type Dissapears when under load [SE-7807]

  • API created with auto discovery from RAML 1.0 spec with includes doesn’t attach includes [SE-5486]

  • Cross-site scripting (reflected) [SE-7930]

March 28, 2018

3.9.0 Runtime Update comes with the following fixes:

  • Dynamic flow reference from a For-Each causes 'ConcurrentModificationException' [SE-7060]

  • SAXParseException when customer is using schema validation in CXF and schema has dependency on other schemas [SE-6358]

  • Mime Type Dissapears when under load [SE-7807]

  • API created with auto discovery from RAML 1.0 spec with includes doesn’t attach includes [SE-5486]

  • DataWeave transformation throws BufferUnderflowException [SE-7263]

  • Cross-site scripting (reflected) [SE-7930]

  • Warning logs are emitted when using secured properties [SE-7445]

March 26, 2018

3.8.6 Runtime Update comes with the following fix:

  • Warning logs are emitted when using secured properties [SE-7445]

March 22, 2018

3.9.0 Runtime Update comes with the following fixes:

  • Fixes an issue where logs are filled up with "skip invalid notification" message when insight is enabled [SE-7552]

  • Fixes an issue where dates weren’t being validate [SE-7622]

  • Fixes NPE thrown by the raml java parser [RP-253]

March 21, 2018

3.8.6, 3.8.5, 3.8.4, and 3.8.1 Runtime Updates come with the following enhancement:

  • Adds more properties in batch notifications when using Insights

February 26, 2018

3.9.0 and 3.8.6 Runtime Updates comes with the following fixes:

  • Fixes an issue where Rate-limiting SLA Based policy applied inconsistently [SE-7099]

  • Fixes a deadlock caused by Grizzly library [SE-7388]

  • Fixes an issue with Concurrent Refresh token requests [SE-7615]

3.9.0 Runtime Update comes with the following fixes:

  • Fixes an issue where STFP Reconnect throws incorrect error [SE-6658]

  • Fixes an issue where Automatic retry on remote Closed exception does not respect RFC 7320 [SE-7116]

February 1, 2018

3.9.0 and 3.8.5 Runtime Update comes with the following improvement:

  • Fixes a performance overhead added by APIKit Router [APIKIT-1146]

January 24, 2018

3.8.6 Runtime Update comes with the following improvements:

  • Fixes a performance overhead added by APIKit Router [APIKIT-1146]

  • Fix unwanted Java warning messages when using secure properties

January 15, 2018

3.8.3 Runtime Update comes with the following fix:

  • kernel-level patch to the operating system to protect against the Speculative Execution vulnerability (CVE-2017-5754)

3.9.0 Runtime Update comes with the following improvements:

  • Fixes an issue where the RAML java parser fails parsing a DataType that import a library [SE-7329]

  • Fixes an incorrect processing of query parameters by APIKit [SE-7407]

January 5, 2018

The following runtime updates includes a kernel-level patch to the operating system to protect against the Speculative Execution vulnerability (CVE-2017-5754).

  • 4.0.0

  • 3.9.0

  • 3.8.6

  • 3.8.5

  • 3.8.4

  • 3.7.5

  • 3.5.4

  • 2.2.1-API-Gateway

December 20, 2017

3.8.6 Runtime Update comes with the following fix:

  • Updated the version of Object Store plugin to respect the request timeout configuration value from Mule

December 12, 2017

3.9.0 Runtime Update comes with the following fix:

  • Fixes an issue that API Gateway shows unwanted log line [SE-7087]

3.8.5 Runtime Update comes with the following improvement:

  • Set HeapMemoryManager as Default Grizzly Memory Manager [MULE-12745]

  • Fixes an issue where APIKit incorrectly overrides the default transformation graph [APIKIT-1092]

November 14, 2017

3.9.0 and 3.8.5 Runtime Update comes with the following fix:

  • Fixes the failure that occurs when attempting to access an XSD file with WSDL with an HTTP/HTTPS base path [MULE-13934]

3.8.5 and 3.8.4 Runtime Update comes with the following fix:

  • Fixes an issue where ObjectToJMSMessage does not register source types [MULE-13974]

3.8.5 Runtime Update comes with the following fix:

  • Fixes an issue where SFTP logging does not mask credentials with special regex chars in password [MULE-13978]

3.8.4 Runtime Update comes with the following fix:

  • Fixes an issue where APIKit incorrectly overrides the default transformation graph [APIKIT-1092]

November 6, 2017

3.9.0, 3.8.5, and 3.8.4 Runtime updates come with the following fix:

  • Fixes an issue where PollingReceiverWorker did not clean RequestContext after performing a poll [MULE-13698]

3.8.5 and 3.8.4 Runtime updates come with the following fixes:

  • Fixes an issue where setting inboundValidationMessage to true in SOAP kit resulted in the error cannot be cast to org.codehaus.stax2.XMLStreamReader2 [MULE-13167]

  • Fixes a problem where CXF Proxy throws NPE when schemas are imported in a WSDL [MULE-7794]

3.8.5 Runtime update comes with the following fix:

  • Fixes an issue where SFTP DSA verification is rejected as an invalid verification code using JDK 1.8.0_121 onwards [MULE-13465]

October 24, 2017

3.8.3 Runtime Update comes with the following fixes:

  • Fix the issue where Replay does not work with DataWeave, VM, Transformers and HTTPS requests [SE-6653,4475,6508,6681]

  • Fixes an issue where calls to multiple DNS servers were being made simultaneously

October 18, 2017

3.8.2 Runtime Update comes with the following fix:

  • Fix the issue where Replay does not work with DataWeave, VM, Transformers and HTTPS requests [SE-6653,4475,6508,6681]

October 17, 2017

3.9.0 is now available in Cloudhub

October 5, 2017

3.8.5 Runtime Updates comes with following fix:

  • Propagation of SSL prevents Jackson serialization of InboundProperties

  • CORS policy is missing Access-Control-Expose-Header support for simple requests

  • Avoid unnecessary wrapping of inbound endpoints with GatewayMessageSource

  • XSD’s imported in WSDL referenced as bare file results in warning while creating request body

  • Fix the issue where Replay does not work with DataWeave, VM, Transformers and HTTPS requests [SE-6653,4475,6508,6681]

October 2, 2017

3.8.3 Runtime Updates comes with following fix:

  • Propagation of SSL prevents Jackson serialization of InboundProperties

September 17, 2017

3.8.3 Runtime Updates comes with following fix:

  • OAuth Module with TLS causing Leak [SE-6762]

September 15, 2017

3.8.1, 3.8.2, 3.8.3, 3.8.4, 3.8.5 Runtime Updates come with following fix:

  • Fix to avoid an incorrect processing of query parameters by the RAML java parser [SE-6751]

September 13, 2017

3.8.3, 3.8.5 Runtime Updates come with the following fix:

  • Fixes an issue where Cloudhub Mule Monitor dies and prevent restart [SE-6649]

3.8.3 Runtime Update comes with the following fixes:

  • Fixes an issue where Event Tracking blocks Message Source thread [SE-6147]

  • Fixes a problem where Worker Unresponsive alert is triggered on a healthy worker [SE-6365]

September 8, 2017

3.7.5 Runtime Update comes with the following improvements:

  • Fixes an issue where Event Tracking blocks Message Source thread [SE-6147]

  • Fixes a problem where Worker Unresponsive alert is triggered on a healthy worker [SE-6365]

August 29, 2017

3.8.5 Runtime Update comes with the following improvements:

  • Fixes an issue where Event Tracking blocks Message Source thread [SE-6147]

  • Fixes a problem where Worker Unresponsive alert is triggered on a healthy worker [SE-6365]

August 4, 2017

3.8.5 Runtime Update comes with the following improvements:

  • Better logging for Replay Transactions

  • Increased retries for storing replay data

  • Added request timeout for storing replay data

  • Increased maximum payload size for replay transactions

3.7.0, 3.7.1, 3.7.2, 3.7.3, 3.7.4, 3.7.5 Runtime Updates come with the following improvement:

  • Support for Persistent Queues in new regions

August 1, 2017

3.8.0, 3.8.1, 3.8.2, 3.8.4 Runtime Updates come with following fix:

  • Fixes an issue with Persistent Queues raising java.lang.NoSuchMethodError [SE-6421]

July 27, 2017

3.8.3 and 3.8.5 Runtimes Update comes with the following fix:

  • Fixes an issue with Persistent Queues raising java.lang.NoSuchMethodError [SE-6421]

3.8.5 Runtime Update comes with the following fix:

  • Fixes a problem where dw-buffer-input*.tmp file is getting created in tmp directory [SE-6424]

  • Fixes an issue where API Console does not render in Studio [FV-103]

  • Fixes an issue where Includes with absolute paths are not resolved in Studio [APIKIT-888]

  • Fixes an issue where APIKit examples were not being generated taking into account the response mimetype [APIKIT-752]

July 19, 2017

3.8.4 Runtime Update comes with the following fix:

  • Fixes a configuration problem that prevented HTTP Request responseTimeout from being honored when doing non-preemptive authentication HTTP calls and caused the HTTP requester to throw an exception if the remote side sends a close connection header

July 13, 2017

3.8.0, 3.8.1, 3.8.2, 3.8.3 and 3.8.4 Runtime Update comes with the following fix:

  • Updated Amazon SDK to 1.11.153

3.8.4 Runtime Update also comes with the following fixes:

  • Fixes an issue where HTTP Request responseTimeout is not honored when doing non-preemptive authentication HTTP call [MULE-12943]

  • Fixes an issue related CORS policy when different versions of the same API are deployed in one application

  • Fixes a problem where HTTP requester throws exception if the remote side sends a close connection header

  • Added support for WS-Security with CXF [MULE-12995]

  • Fixes performance issues related to RAML 1.0 Parser

June 22, 2017

3.8.4 Runtime Update comes with the following fix:

  • Fixes Performance Degradation due to MVEL optimizer not refreshing when the payload type changes MULE-11274 and MULE-12718.

  • Upgrade JDK to 8u131.

May 18, 2017

3.8.4 Runtime Update comes with the following fixes:

  • Fixes an issue where Multiple JDBC Connector in foreach scope component cause null pointer due to NotificationUtils not checking for null parentElement [MULE-12267]

  • Fixes a problem where XsltTransformer should close underlying InputStream when using XMLStreamReader [MULE-12360]

  • Fixes an issue of race condition in batch when the thread dispatcher reads from the persistent queue which leads to delayed processing in a batch process

  • Fixes an issues related to high CPU due to infinite loop in a batch job

  • Fixes a problem where com.mulesoft.weave.model.values.NameValue$MaterializedNameValue cannot be cast to com.mulesoft.weave.model.capabilities.AttributesCapablet

  • Fixes an issue where large payload is getting dropped while performing only set-variable DW transform

May 9, 2017

3.8.3 Runtime Update comes with the following fix:

  • Fixes an issue where MuleWeaveFactory$.createGlobalContext(…​) blocks threads

May 2, 2017

3.8.4 Runtime Update comes with the following fixes:

  • Fixes a problem where token refresh overrides payload when resending request [MULE-11949]

  • Fixes issue where SedaStageInterceptingMessageProcessor thread should clear RequestContext [MULE-12206]

  • Fixes an issue where MuleWeaveFactory$.createGlobalContext(…​) blocks threads

  • Fixes a problem with High CPU usage caused by internal configuration

3.8.3 Runtime Update comes with the following fixes:

  • MVEL optimizer does not refresh when the payload type changes [MULE-11274]

April 12, 2017

3.8.4 runtime update

March 21, 2017

This runtime update comes with the following fixes:

  • Fixes an issue where after until-successful flow variables loses mime type [MULE-11382]

  • Fixes a problem with DataWeave FlatFile transformation not working as expected when unbounded nested segments are in place

  • Fixes an issue with HTTP requester when sending request to Microsoft IIS

  • Fixes a problem where Oauth authentication uses refreshToken when parameter is overriding payload [MULE-11949]

  • Fixes an issue where Mule Listener stopped serving request after one grizzly listener is killed due to NoClassDefFoundError [MULE-11337]

These updates are available for Mule Runtime version 3.8.3.

March 2, 2017

Patched API Gateway 2.2.0 with MULE-9163 fix.

February 7, 2017

Patched 3.8.x runtimes to upgrade to Python 3 and accommodate to AWS new instances id (long id).

December 1, 2016

This set of runtime updates includes the following:

  • Fixes a vulnerability with JAXB and Jersey which could result in a DoS attack

  • Fixes a problem where a 403 error would appear in the logs when using Insight

These updates will be released for the following versions: 3.5.0, 3.5.1, 3.5.2, 3.5.3, 3.5.4, 3.6.0, 3.6.1, 3.6.2, 3.6.3, 3.6.4, 3.7.0, 3.7.1, 3.7.2, 3.7.3, 3.7.4, 3.8.0, 3.8.1, 3.8.2, API Gateway 2.0.2, API Gateway 2.0.3, API Gateway 2.0.4, API Gateway 2.1.0, API Gateway 2.1.1, API Gateway 2.2.0

November 23, 2016

This set of runtime updates includes the following:

  • Fixes a vulnerability with JAXB and Jersey which could result in a DoS attack

  • Fixes a problem where a 403 error would appear in the logs when using Insight

  • Fixes an issue with DataWeave which would result in running out of space on the drive for 3.8.x

  • Fixes an issue with APIkit where it would cast a numeric string query param to Integer, which then caused a InvalidQueryParameterException

Runtimes updated include 3.5.4, 3.7.4, and 3.8.2