CloudHub Runtime and Operating System Patch Update Release Notes

link管理

链接快照平台

输入网页链接，自动生成快照
标签化管理网页链接

Create connected experiences with AI

Learn the critical steps to developing an AI strategy and foundation.

Future of connected AI agents

Discover how to prepare for the future of autonomous AI agents.

See all resources

The world of AI is a world of APIs

Relive the best moments from Connect:AI with 20+ on-demand sessions.

Start watching

See all

See all solutions

Create connected experiences with AI

Learn the critical steps to developing an AI strategy and foundation.

Future of connected AI agents

Discover how to prepare for the future of autonomous AI agents.

See all resources

The world of AI is a world of APIs

Relive the best moments from Connect:AI with 20+ on-demand sessions.

Start watching

Free trial

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:

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:

NullPointerException is no longer thrown when DataWeave transforms a RetryPolicyExhaustedException to a JSON format on a Java 17 runtime.

W-15643200

Properties files are now located in the lib/user directory during application deployment.

W-16404468

com.google.gson.stream.MalformedJsonException is no longer thrown while deploying an application.

W-16343071

Kryo serialization now works as expected with ResourceOwnerOAuthContextWithRefreshState when using Java 17.

W-16533466

Debug logs for custom policies containing a custom extension/connector now work correctly.

W-15286605

The process of unloading native libraries in Windows OS running on Java 8 and Java 11 is now improved.

W-16375439

ChainInputResolver annotations are no longer ignored when there are no input, output, or metadata keys resolvers in Java SDK.

W-16408471

Policies with minimum Mule version 4.4.0 now use the flow name as part of the artifact name, when the feature flag anypoint.platform.keep.default.policy.format=true is set.

W-16169887

NullPointerException is no longer thrown when API Gateway tries to dispose an empty cluster.

W-16540685

API Gateway pollers are no longer initialized when the API Gateway is started in offline mode.

W-16093885

Log warning "Unable to dispose not present 'ByteBufferProvider org.mule.weave.v2.memory.service'" is no longer thrown while disposing a policy.

W-16263266

NullPointerException is no longer thrown when DataWeave transforms a RetryPolicyExhaustedException to a JSON format on a Java 17 runtime.

W-15643200

Properties files are now located in the lib/user directory during application deployment.

W-16404468

com.google.gson.stream.MalformedJsonException is no longer thrown while deploying an application.

W-16343071

Kryo serialization now works as expected with ResourceOwnerOAuthContextWithRefreshState when using Java 17.

W-16533466

Debug logs for custom policies containing a custom extension/connector now work correctly.

W-15286605

The process of unloading native libraries in Windows OS running on Java 8 and Java 11 is now improved.

W-16375439

Policies with minimum Mule version 4.4.0 now use the flow name as part of the artifact name, when the feature flag anypoint.platform.keep.default.policy.format=true is set.

W-16169887

NullPointerException is no longer thrown when API Gateway tries to dispose an empty cluster.

W-16540685

API Gateway pollers are no longer initialized when the API Gateway is started in offline mode.

W-16093885

Debug logs for custom policies containing a custom extension/connector now work correctly.

W-15286605

Policies with minimum Mule version 4.4.0 now use the flow name as part of the artifact name, when the feature flag anypoint.platform.keep.default.policy.format=true is set.

W-16169887

NullPointerException is no longer thrown when API Gateway tries to dispose an empty cluster.

W-16540685

API Gateway pollers are no longer initialized when the API Gateway is started in offline mode.

W-16093885

DataWeave

DataWeave now preserves MimeType properties correctly.

W-16161736

java.lang.NoSuchFieldError: id_alg_AEADChaCha20Poly1305 is no longer thrown when using the Message Encryption Processor.

W-16461398

Loaded native libraries are now copied into a separate temporary folder to avoid issues while redeploying applications in Windows OS.

W-15894519

Parameter resolution error handling is no longer affected when the parameterized operation is inside a dynamically referenced subflow.

W-15923581

The OAuth token invalidation status is now communicated to other nodes in a cluster when a token is invalidated on one node.

W-15154658

Flows now honour the state configured in flows.deployment.properties when restarting the app, regardless of the initial state. To enable this feature, use the mule.honour.persisted.flow.state system property. This only applies to Standalone and Hybrid deployments.

W-15750334

A serialization exception is no longer thrown when a Batch Step fails with a ModuleException in Java 17.

W-15808825

mule-script-module is now improved to ensure that beans no longer contain invalid references to injected dependencies, whether they are directly or indirectly reliant on MuleConfiguration.

W-15832941

Jars in lib/user are now visible from jars in lib/opt . For example, using cluster persistence with the JDBC driver provided in lib/user no longer fails with a Could not load driverClass error .

W-16010357

Serialization now works as expected with Batch Job and Salesforce BulkOperationResult in Java 17.

W-16105403

Batch module no longer fails with a Could not serialize object error when client ID enforcement policy is enabled.

W-16124318

ClassNotFoundException is no longer thrown when upgrading from Mule runtime 4.4.0 using the OAuth 2 authentication code and Object Store V2 stored tokens.

W-15595791

NullPointerException no longer occurs when having MQ connector as a dependency in MUnit 3.1.0.

W-15734679

NullPointerException no longer occurs while packaging an application with global on-error references.

W-16083021

Hard timeout for platform requests is now available by setting up the anypoint.platform.request_timeout in milliseconds.

W-16141554

DataWeave

Argument materialization is now improved at the dw::Runtime::try function.

W-15323897

Streaming capability is now enabled for arguments of sum , countBy , and sumBy functions.

W-16125755

Loaded native libraries are now copied into a separate temporary folder to avoid issues while redeploying applications in Windows OS.

W-15894519

Parameter resolution error handling is no longer affected when the parameterized operation is inside a dynamically referenced subflow.

W-15923581

The OAuth token invalidation status is now communicated to other nodes in a cluster when a token is invalidated on one node.

W-15154658

W-15750334

A serialization exception is no longer thrown when a Batch Step fails with a ModuleException in Java 17.

W-15808825

mule-script-module is now improved to ensure that beans no longer contain invalid references to injected dependencies, whether they are directly or indirectly reliant on MuleConfiguration.

W-15832941

W-16010357

Serialization now works as expected with Batch Job and Salesforce BulkOperationResult in Java 17.

W-16105403

Batch module no longer fails with a Could not serialize object error when client ID enforcement policy is enabled.

W-16124318

ClassNotFoundException is no longer thrown when upgrading from Mule runtime 4.4.0 using the OAuth 2 authentication code and Object Store V2 stored tokens.

W-15595791

NullPointerException no longer occurs when having MQ connector as a dependency in MUnit 3.1.0.

W-15734679

Hard timeout for platform requests is now available by setting up the anypoint.platform.request_timeout in milliseconds.

W-16141554

DataWeave

Argument materialization is now improved at the dw::Runtime::try function.

W-15323897

Streaming capability is now enabled for arguments of sum , countBy , and sumBy functions.

W-16125755

Loaded native libraries are now copied into a separate temporary folder to avoid issues while redeploying applications in Windows OS.

W-15894519

Parameter resolution error handling is no longer affected when the parameterized operation is inside a dynamically referenced subflow.

W-15923581

The OAuth token invalidation status is now communicated to other nodes in a cluster when a token is invalidated on one node.

W-15154658

W-15750334

Hard timeout for platform requests is now available by setting up the anypoint.platform.request_timeout in milliseconds.

W-16141554

The mule-assembly-content-descriptor file size no longer differs between mule-ee-distribution-standalone ZIP and Tar GZ distributions.

W-15397610

The redeployment of an app with a domain using a Groovy component no longer throws the groovy.lang.MissingMethodException exception.

W-15750766

Cache scope with multiple computations no longer occurs if events arrive concurrently for an absent key.

W-14604517

MUnit tests no longer fail with groupId cannot be null when using a parent POM for dependencies and plugins.

W-14998254

DataWeave compiled expressions cache is no longer overpopulated when using nested templates.

W-15782010

Kerberos is now enabled for proxy authentication against Anypoint Platform for Gateway capabilities.

W-15642605

Default stronger validations for policies are now added after applying the property anypoint.platform.validate_policy_schemas .

W-15769926

Default gatekeeping for APIs that fail when doing a rollback is now added using the property anypoint.platform.gatekeeper.block_failed_revert .

W-15427352

Deploying an application with Mule SDK scope and policies no longer throws the NoSuchElementException: No 'componentIdentifier' set for location exception message.

W-15980586

DataWeave

Enforced Java accessibility restrictions only for Mule apps with DataWeave language level version 2.6 and later and executing with Java 17 and later.

W-15832793

The mule-assembly-content-descriptor file size no longer differs between mule-ee-distribution-standalone ZIP and Tar GZ distributions.

W-15397610

The redeployment of an app with a domain using a Groovy component no longer throws the groovy.lang.MissingMethodException exception.

W-15750766

Cache scope with multiple computations no longer occurs if events arrive concurrently for an absent key.

W-14604517

MUnit tests no longer fail with groupId cannot be null when using a parent POM for dependencies and plugins.

W-14998254

Kerberos is now enabled for proxy authentication against Anypoint Platform for Gateway capabilities.

W-15642605

Default stronger validations for policies are now added after applying the property anypoint.platform.validate_policy_schemas .

W-15769926

Default gatekeeping for APIs that fail when doing a rollback is now added using the property anypoint.platform.gatekeeper.block_failed_revert .

W-15427352

DataWeave

Enforced Java accessibility restrictions only for Mule apps with DataWeave language level version 2.6 and later and executing with Java 17 and later.

W-15832793

The mule-assembly-content-descriptor file size no longer differs between mule-ee-distribution-standalone ZIP and Tar GZ distributions.

W-15397610

The redeployment of an app with a domain using a Groovy component no longer throws groovy.lang.MissingMethodException exception.

W-15750766

Cache scope with multiple computations no longer occurs if events arrive concurrently for an absent key.

W-14604517

Kerberos is now enabled for proxy authentication against Anypoint Platform for Gateway capabilities.

W-15642605

Default stronger validations for policies are now added after applying the property anypoint.platform.validate_policy_schemas .

W-15769926

Default gatekeeping for APIs that fail when doing a rollback is now added using the property anypoint.platform.gatekeeper.block_failed_revert .

W-15427352

DataWeave

The Flat File module now adds the substituteCharacterAsMissingValue reader property.

W-15571377

The mule-assembly-content-descriptor file size no longer differs between mule-ee-distribution-standalone ZIP and Tar GZ distributions.

W-15397610

The redeployment of an app with a domain using a Groovy component no longer throws the groovy.lang.MissingMethodException exception.

W-15750766

DataWeave compiled expressions cache is no longer overpopulated when using nested templates.

W-15782010

Kerberos is now enabled for proxy authentication against Anypoint Platform for Gateway capabilities.

W-15642605

Default stronger validations for policies are now added after applying the property anypoint.platform.validate_policy_schemas .

W-15769926

Default gatekeeping for APIs that fail when doing a rollback is now added using the property anypoint.platform.gatekeeper.block_failed_revert .

W-15427352

You can now see the number of flows considered for UBP and what those flows are when the application starts.

W-14401338

The exception java.lang.IllegalAccessException no longer occurs when using itemSequenceInfo in DataWeave.

W-15617764

DataWeave compiled expressions cache is no longer overpopulated when using nested templates.

W-15782010

NullPointerException no longer occurs on AST-deserialized applications using Anypoint Custom Metrics Connector.

W-15677894

A java.io.IOException exception no longer occurs when writing the same binary input multiple times for JSON and XML formats.

W-14589732

When comparing a Date with a String representation of a date, the Date format is now used to coerce the String accordingly.

W-15478713

An application using a global error handler from an imported module no longer throws NullPointerException on startup.

W-16019352

Passing system property arguments and running on Java 11 or later on CE distribution now work as expected.

W-14998262

JSON schema draft version is now properly enforced. For example, the id field in draft-07 is ignored as it must be defined as $id .

W-14808949

The exception java.lang.IllegalAccessException no longer occurs when using itemSequenceInfo in DataWeave.

W-15617764

You can now see the number of flows considered for UBP and what those flows are when the application starts.

W-14401338

NullPointerException no longer occurs on AST-deserialized applications using Anypoint Custom Metrics Connector.

W-15677894

DataWeave

Validation for type parameter usage in non-generic types now works as expected.

W-15206030

A java.io.IOException exception no longer occurs when writing the same binary input multiple times for JSON and XML formats.

W-14589732

When comparing a Date with a String representation of a date, the Date format is now used to coerce the String accordingly.

W-15478713

You can now see the number of flows considered for UBP and what those flows are when the application starts.

W-14401338

The exception java.lang.IllegalAccessException no longer occurs when using itemSequenceInfo in DataWeave.

W-15617764

DataWeave compiled expressions cache is no longer overpopulated when using nested templates.

W-15782010

NullPointerException no longer occurs on AST-deserialized applications using Anypoint Custom Metrics Connector.

W-15677894

A java.io.IOException exception no longer occurs when writing the same binary input multiple times for JSON and XML formats.

W-14589732

When comparing a Date with a String representation of a date, the Date format is now used to coerce the String accordingly.

W-15478713

DataWeave compiled expressions cache is no longer overpopulated when using nested templates.

W-15782010

A java.io.IOException exception no longer occurs when writing the same binary input multiple times for JSON and XML formats.

W-14589732

When upgrading a policy, templates are now downloaded before the previous version is removed.

W-15212679

When applying a policy that initially failed but was later applied successfully, the retry initiated by the gateway no longer causes an exception error.

W-15186491

Getting metadata from a XSD with vc:minVersion=1.1 no longer causes a NullPointerException error.

W-15193303

DataWeave

ArithmeticException no longer executes toHex with non-integer numbers.

W-15006840

Using vc:minVersion="1.1" in XSD schema no longer throws NullPointerException in XML SDK connectors.

W-15081363

Inconsistent behavior no longer occurs between in-memory and streaming XML parsers for deciding document encoding.

W-15110015

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

W-14646484

Using vc:minVersion="1.1" in XSD schema no longer throws NullPointerException in XML SDK connectors.

W-15081363

Explicit socket connection timeout for socket creation with the management plane no longer occurs.

W-14555248

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

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

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

W-14128870

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.

For information, see Runtime Manager Agent 1.15.13 Release Notes , Runtime Manager Agent 2.5.9 Release Notes and Runtime Manager Agent 2.6.0 Release Notes .

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

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

W-14748090

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

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

W-14391247

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

W-14514837

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

W-14417598

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.

For information, see Runtime Manager Agent 1.15.13 Release Notes and Runtime Manager Agent 2.5.9 Release Notes .

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.

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

W-14479183

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

W-14350781

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

W-14555248

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.

For information, see Runtime Manager Agent 1.15.13 Release Notes and Runtime Manager Agent 2.5.8 Release Notes .

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.

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.

For information, see Runtime Manager Agent 1.15.13 Release Notes and Runtime Manager Agent 2.5.6 Release Notes .

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.

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

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

W-13038823

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

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

W-13805995

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

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

W-13805995

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

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.

For information, see Runtime Manager Agent 1.15.13 Release Notes and Runtime Manager Agent 2.5.3 Release Notes .

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.

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

This release adds the enforce.dw.expression.validation flag that, when enabled, enforces all DataWeave expressions.

MULE-19967

DataWeave

The typeOf function now returns the underlying type value.

W-10648848

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

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

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 StackOverflow error on recursive function call with Object type argument no longer occurs.

W-13635914

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 @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 function dw::core::Binaries::concatWith that allows the concatenation of two Binary values is now added.

DW-882

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

W-13858445

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

W-11965399

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.

For information, see Runtime Manager Agent 1.15.13 Release Notes and Runtime Manager Agent 2.5.4 Release Notes .

Fixed Issues

4.4.0 Runtime Updates

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

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.

For information, see Runtime Manager Agent 1.15.13 Release Notes and Runtime Manager Agent 2.5.3 Release Notes .

Fixed Issues

4.4.0 Runtime Updates

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

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.

For information, see Runtime Manager Agent 1.15.13 Release Notes and Runtime Manager Agent 2.5.1 Release Notes .

Fixed Issues

4.4.0 Runtime Updates

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

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

W-13509911

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

W-13563214

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

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

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

W-12975498

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.

For information, see Runtime Manager Agent 1.15.13 Release Notes and Runtime Manager Agent 2.5.1 Release Notes .

Fixed Issues

4.4.0 Runtime Updates

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

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.

For information, see Runtime Manager Agent 1.15.13 Release Notes and Runtime Manager Agent 2.5.1 Release Notes .

Fixed Issues

4.4.0 Runtime Updates

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

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

W-12452407

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

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

W-10619784

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

W-10619792 / MULE-19874

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

W-12436154

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

W-12623414

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.

For information, see Runtime Manager Agent 1.15.13 Release Notes and Runtime Manager Agent 2.5.0 Release Notes .

Fixed Issues

4.4.0 Runtime Updates

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

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

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

W-12377294

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

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

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

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

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

W-11577522

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

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

W-12517872

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.

For information, see Runtime Manager Agent 1.15.13 Release Notes and Runtime Manager Agent 2.4.37 Release Notes .

Fixed Issues

4.4.0 Runtime Updates

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

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

W-12206167

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

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

W-12129696

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

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

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

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

W-11920598

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

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

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

W-12234425

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

W-11620156

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

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

W-11529823

W-12036336

W-12472890

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

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

W-12049036

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

W-12049036

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.

For information, see Runtime Manager Agent 1.15.13 Release Notes and Runtime Manager Agent 2.4.34 Release Notes .

Fixed Issues

4.4.0 Runtime Updates

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

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

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

W-11603893

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

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

W-10822938

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

W-10634129

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.

For information, see Runtime Manager Agent 1.15.13 Release Notes and Runtime Manager Agent 2.4.34 Release Notes .

Fixed Issues

4.4.0 Runtime Updates

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

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

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

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

W-11741912

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

W-11620006

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.

For information, see Runtime Manager Agent 1.15.12 Release Notes and Runtime Manager Agent 2.4.33 Release Notes .

Fixed Issues

4.4.0 Runtime Updates

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

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

W-11265408

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

W-11507190

These releases include Runtime Manager Agent 1.15.12 for Runtime 3.9.5, and Runtime Manager Agent 2.4.32 for Runtime 4.3.0 and 4.4.0.

For information, see Runtime Manager Agent 1.15.12 Release Notes and Runtime Manager Agent 2.4.32 Release Notes .

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

W-11324527

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

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

W-11203794

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

W-11324530

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

These releases include Runtime Manager Agent 1.15.12 and Runtime Manager Agent 2.4.30.

For information, see Runtime Manager Agent 1.15.12 Release Notes and Runtime Manager Agent 2.4.30 Release Notes .

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

W-11193698

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

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

W-11210176/SE-19542

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

W-11210176/SE-19542

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

W-11210176/SE-19542

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

W-11210176/SE-19542

These releases include Runtime Manager Agent 1.15.11 and Runtime Manager Agent 2.4.28.

For information, see Runtime Manager Agent 1.15.11 Release Notes and Runtime Manager Agent 2.4.28 Release Notes .

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

W-11172835

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

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

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

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

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

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

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

W-10935528

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

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

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

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

W-10818822

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

W-10818822

These releases include Runtime Manager Agent 1.15.11 and Runtime Manager Agent 2.4.27.

For information, see Runtime Manager Agent 1.15.11 Release Notes and Runtime Manager Agent 2.4.27 Release Notes .

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

SE-24186

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

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

W-10619599 / MULE-20072 / SE-24241

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

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

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

DW-1080

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

SE-23802

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

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

MULE-20024/SE-22842

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

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

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

EE-8140/SE-21240

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

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

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

SE-22434

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

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

MULE-19848/SE-2228

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

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

DW-932

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

SE-22431

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

SE-23483

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

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

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

SE-22434

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

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

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

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

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

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

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

SE-23500

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

SE-23500

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

SE-23500

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

SE-23500

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.

For more information about this patch update, see HTTP Redirect Known Issues in Mule 4.3 and 4.4 runtime engines - November 2021 changes .

Fixed Issues

4.4.0 Runtime Updates

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

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

MULE-19811

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

MULE-19678

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

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

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

SE-21464

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

SE-17741

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

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

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

SE-17741

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

SE-17741

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

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

SE-22333

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

SE-11533

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

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

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

SE-20614

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 warning when using the design-time only format application/dw without dataOnly mode.

DW-873

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

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

DW-309

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

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

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

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

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

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

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

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.

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.

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.

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.

To address this change, see Change of Behavior with DataWeave Functionality on May 4, 2021 .

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.

For an upcoming release in May, the behavior of the DataWeave XML reader functionality will change.

This change will affect Mule versions 3.9.5, 4.1.6, 4.2.2, and 4.3.0 for on-premises Mule, CloudHub, and other hosted or embedded runtimes, including Anypoint Runtime Fabric and Anypoint Studio.

To prepare for this change, see Change of Behavior with DataWeave Functionality on May 4, 2021 .

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.

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

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.

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

The corresponding response contains the Connection: close header.

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

This change is needed for redeployments.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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

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)

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

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)

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)

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

To work around this issue, remove the entryTtl and entryTtlUnit properties from the object store definition.

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)

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)

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

To work around this issue, remove the entryTtl and entryTtlUnit properties from the object store definition.

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)

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)

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)

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)

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)

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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)

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)

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)

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)

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)

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)

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)

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.

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)

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)

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)

Fixed an issue that caused FlowStack : <empty> log messages with invalid expressions. (SE-13660)

Fixed an issue that occurred when the Scatter-Gather component contained Flow References.

Fixed an issue that affected the OAuth token refresh.

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)

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)

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)

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)

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.

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]

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]

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]

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]

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]

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]

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]

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]

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]

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

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]

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

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

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]

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]

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]

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]

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]

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]

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]

Fix Policies that manage client applications not working as expected when encryption is configured.

Faster application deployment with Monitoring feature disabled.

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]

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]

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]

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 .

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]

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]

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]

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]

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 .

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 .

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]

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]

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]

Update object store plugin to provide better reconnection strategy on socket timeout exception

Fix Anypoint Visualizer enablement for cached instances

Update object store plugin to provide better reconnection strategy on socket timeout exception

Fix Anypoint Visualizer enablement for cached instances

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]

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

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]

API created with auto discovery from RAML 1.0 spec with includes doesn’t attach includes [SE-5486]

Cross-site scripting (reflected) [SE-7930]

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]

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]

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]

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]

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

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]

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]

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

Fixes Performance Degradation due to MVEL optimizer not refreshing when the payload type changes MULE-11274 and MULE-12718.

Upgrade JDK to 8u131.

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

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

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]

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