Contact Free trial Login

CloudHub Runtime and Operating System Release Notes

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

In addition to these release notes, see:

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

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

November

November 3

November 16-20

November 21-22

October

October 8 (4.3.0 only, OS only)

October 6

October 19-23

October 24-25

September

September 8

September 21-24

September 26-27

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

October 8, 2020

4.3.0 Runtime Update

  • Updated to the latest operating system security patches.

October 6, 2020

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

  • Updated to the latest operating system security patches.

4.2.2 Runtime Update

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

Issue Description

MULE-18573/SE-15592

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

MULE-18742

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

MULE-18164/SE-14610

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

SE-15624

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

MULE-17725/SE-15590

Resolved an issue in which a configuration property value for a key could not be found after restarting the domain.

MULE-17880/SE-12712

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

AGW-4336

Resolved a problem in which client ID and client secret expressions were incorrectly processed by the encryption engine when applying the Client ID Enforcement policy with the policy encryption mode set to SENSITIVE_ONLY.

SE-16350

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

SE-13440

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

SE-17212

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

MULE-18047/MULE-18634

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

MULE-18687

Resolved an issue in which an HTTP request with an invalid OAuth token sometimes hung.

4.2.1 Runtime Update

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

Issue Description

MULE-18573/SE-15592

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

MULE-18657/SE-14959

Fixed a problem that prevented primary node initialization in Anypoint Connector for Salesforce (Salesforce Connector).

MULE-18164/SE-14610

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

SE-15624

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

MULE-18047/MULE-18634

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

MULE-16897

Resolved an issue that occurred with cluster primary-node listener activity after agent initialization.

4.1.6 Runtime Update

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

Issue Description

SE-16282

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

4.1.5 Runtime Update

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

Issue Description

SE-16282

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

EE-7097/SE-11533

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

SE-17812

Fixed a problem that caused the following error:

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

3.8.7 Runtime Update

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

Issue Description

SE-17299

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

SE-7717

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

September 8, 2020

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

  • Updated to the latest operating system security patches.

  • Updated to the latest JDK 8 minor version.

4.3.0 Runtime Update

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

Issue Description

MULE-18694/SE-16719

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

MULE-18666

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

#[output application/json --- message]

MULE-18689/SE-16734

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

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

MULE-18682

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

MULE-18657/SE-14959

Fixed a problem that prevented primary node initialization in Anypoint Connector for Salesforce (Salesforce Connector).

MULE-18665/SE-16278

Fixed the RegistryLifecycleCallback logger so that it no longer prints the customer’s security key.

MULE-18542/SE-15818

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

MULE-18628/SE-16435

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

MULE-18623/SE-16933

Corrected a memory leak that occurred when using dynamic configurations.

SE-15453

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

SE-15249

Fixed DataWeave attribute selector not dispatching to the correct implementation.

SE-15362

Fixed NullPointerException in DataWeave’s XML module.

DW-184/SE-15834

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

SE-15894

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

SE-16462

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

SE-16539

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

SE-16167

The DataWeave Avro module now correctly converts logical types.

AGW-4287/SE-16981

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

SE-17193

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

SE-17270

Fixed an issue in which the primary node in a cluster remained primary after stopping the runtime, causing applications with a pooling processor on the primary node to stop working.

MULE-18604/SE-12900

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

SE-17080

Fixed an error that occurred when sending a request to an app using OAuth2 authentication with Object Store v2.

SE-17119

Fixed an issue that caused deployments to fail for apps using OAuth2 authentication with Object Store v2.

SE-17454

Fixed an issue in which setting the value of expirationInterval to -1 specified a TTL of 0 seconds (rather than the expected unlimited TTL) and caused the object store to expire immediately.

4.2.2 Runtime Update

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

Issue Description

MULE-18657/SE-14959

Fixed a problem that prevented primary node initialization in Anypoint Connector for Salesforce (Salesforce Connector).

MULE-18665/SE-16278

Fixed the RegistryLifecycleCallback logger so that it no longer prints the customer’s security key.

MULE-18628/SE-16435

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

SE-15067

DataWeave now properly handles the #[ sequence inside a String value in Mule operations, such as Logger.

MULE-18548/SE-14272

Fixed an issue in which the Cache scope in a cluster configuration did not effectively monitor the cache in the secondary node.

MULE-18584/SE-16130

Fixed a memory leak caused by unclosed cursors when used with Foreach loops.

SE-16455

Resolved a memory leak that could cause OutOfMemory errors, which occurred when the app didn’t explicitly nullify the payload at the end of the Foreach loop.

MULE-18604/SE-12900

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

MULE-17987

Fixed a problem that occurred when logging an error for a component that contains a special character, for example, when using the Cryptography module.

MULE-16688

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

MULE-18390

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

SE-13440

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

SE-14220

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

SE-15894

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

SE-16167

The DataWeave Avro module now correctly converts logical types.

SE-16539

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

SE-16620

Resolved an issue in which an AVRO decimal value was incorrectly treated as a string and not a decimal.

SE-17080

Fixed an error that occurred when sending a request to an app using OAuth2 authentication with Object Store v2.

SE-17119

Fixed an issue that caused deployments to fail for apps using OAuth2 authentication with Object Store v2.

SE-17454

Fixed an issue in which setting the value of expirationInterval to -1 specified a TTL of 0 seconds (rather than the expected unlimited TTL) and caused the object store to expire immediately.

4.2.1 Runtime Update

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

Issue Description

SE-16867

Fixed an issue with DataWeave that caused the following error:

You called the function 'AnonymousFunction' with these arguments

MULE-18628/SE-16435

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

MULE-18584/SE-16130

Fixed a memory leak caused by unclosed cursors when used with Foreach loops.

SE-16455

Resolved a memory leak that could cause OutOfMemory errors, which occurred when the payload was not explicitly nullified at the end of the Foreach loop.

MULE-18579/SE-16764

Resolved an issue in which when an object store expired, it loaded all deserialized entries into memory, doubling memory consumption.

MULE-18604/SE-12900

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

MULE-18390

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

SE-17080

Fixed an error that occurred when sending a request to an app using OAuth2 authentication with Object Store v2.

SE-17119

Fixed an issue that caused deployments to fail for apps using OAuth2 authentication with Object Store v2.

SE-17454

Fixed an issue in which setting the value of expirationInterval to -1 specified a TTL of 0 seconds (rather than the expected unlimited TTL) and caused the object store to expire immediately.

4.2.0 Runtime Update

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

Issue Description

SE-17450

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

SE-15624

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

MULE-18573/SE-15592

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

MULE-18047/MULE-18634

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

MULE-18164/SE-14610

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

MULE-18390

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

4.1.6 Runtime Update

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

Issue Description

MULE-18390

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

MULE-18312/SE-13775

Resolved an issue in which running the MUnit test for an application using APIkit failed to upgrade from 4.1.4 to a later version.

MULE-17647/SE-12720

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

SE-13404

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

SE-13429

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

MULE-17096/SE-12340

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

4.1.5 Runtime Update

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

Issue Description

MULE-18390

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

MULE-17863/SE-13533

Resolved an issue in which MUnit tests did not run reliably in a Windows environment when started from the command line or Jenkins due to improper file cleanup.

SE-12095

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

SE-12167

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

SE-11241

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

MULE-16230/SE-10165

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

MULE-16483/SE-10782

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

EE-7358/SE-12434

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

EE-6830/SE-12284

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

3.9.2 Runtime Update

Issue Description

SE-17135

Fixed an issue in which inbound metrics for HTTP-based apps stopped working when auto discovery was enabled.

3.9.1 Runtime Update

Issue Description

SE-17135

Fixed an issue in which inbound metrics for HTTP-based apps stopped working when auto discovery was enabled.

3.9.0 Runtime Update

Issue Description

SE-17135

Fixed an issue in which inbound metrics for HTTP-based apps stopped working when auto discovery was enabled.

3.8.7 Runtime Update

Issue Description

SE-17135

Fixed an issue in which inbound metrics for HTTP-based apps stopped working when auto discovery was enabled.

August 17, 2020

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

  • Updated to the latest operating system security patches (no Mule runtime engine update).

August 4, 2020

4.3.0 Runtime Update

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

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

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

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

  • Resolved an issue in which the Anypoint Connector for Kafka returned the java.nio.file.InvalidPathException: Illegal char <:> exception when accessing filesystem configuration files. (MULE-18569/SE-16282)

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

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

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

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

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

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

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

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

  • The fix for the SE-15056 issue causes applications that use custom policies to fail when sharing the ErrorType repository if the app and policy bundle didn’t include all dependencies.

    You can revert the behavior by setting the mule.share.errorTypeRepository system property to true. (MULE-18196/SE-16894)

  • Fixed an issue in which an application using more than one salesforce:replay-channel operation failed with status code 429. (SE-13603)

  • Upgraded the Object Store v2 plugin to version 4.0.27. (SE-13603/SE-10677/SE-16728)

Known Issues

The 4.3.0 release contains the following known issues with Object Store v2:

  • Two known issues when using OAuth2 authentication with an app with an object store:

    When sending a request to the app, the following error occurs: (SE-17080)

    {"error_description":"Invalid credentials","error":"invalid_client"}%

    When deploying the app, deployment fails with the following error: (SE-17119)

    Partition with name _defaultPersistentObjectStore does not exist in store

    To work around these issues, use the following clientStore configuration:

    <oauth2-provider:config
    	name="Oauth2_Provider_Config" doc:name="Oauth2 Provider Config"
    	doc:id="fbb2f727-5e7d-4cf5-8a84-52de678a017a" providerName="Mulesoft"
    	clientSecurityProvider="${myCompany.oauth.clientSecurityProvider}"
    	supportedGrantTypes="${myCompany.oauth.grantType}"
    	listenerConfig="api-httpListenerConfig" clientStore="Object_store">
  • A known issue with setting the TTL (time to live) value for an object store (SE-17454):

    Setting the value of entryTtl to 0 and the value of expirationInterval to less than or equal to 0 configures the TTL as 0 seconds (rather than the expected unlimited TTL). This behavior causes the object store entries to expire immediately and any operations that are dependent on the key in the app to fail.

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

4.2.2 Runtime Update

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

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

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

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

  • Resolved an issue in which running the MUnit test for an application using APIkit failed to upgrade from 4.1.4 to a later version. (MULE-18312/SE-13775)

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

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

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

  • Resolved a problem in which an application with more than one test suite failed to run MUnit when triggered by a Maven plugin, but ran MUnit correctly in Anypoint Studio. (SE-13426)

  • Fixed a problem in which MUnit tests failed if the app used Object Store after upgrading from Mule 4.2.2 to a later MUnit and Mule runtime release. (SE-15892)

  • Resolved an issue in which MUnit tests did not run reliably in a Windows environment when started from the command line or Jenkins due to improper file cleanup. (MULE-17863/SE-13533)

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

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

  • Resolved an issue in which the Anypoint Connector for Kafka returned the java.nio.file.InvalidPathException: Illegal char <:> exception when accessing filesystem configuration files. (MULE-18569/SE-16282)

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

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

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

  • Resolved a deployment problem that occurred when a policy defined an error handler for an ErrorType issue (such as OS:KEY_NOT_FOUND or HTTP:TIMEOUT) exposed by an extension, and the application defined the same extension.

    The deployment failed because the ErrorType could not be found. (MULE-18284)

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

  • The fix for the SE-15056 issue causes applications that use custom policies to fail when sharing the ErrorType repository if the app and policy bundle didn’t include all dependencies.

    You can revert the behavior by setting the mule.share.errorTypeRepository system property to true. (MULE-18196/SE-16894)

  • Fixed an issue in which an application using more than one salesforce:replay-channel operation failed with status code 429. (SE-13603)

  • Upgraded the Object Store v2 plugin to version 4.0.27. (SE-13603/SE-10677/SE-16728)

Known Issues

The 4.2.2 release contains the following known issues with Object Store v2:

  • Two known issues when using OAuth2 authentication with an app with an object store:

    When sending a request to the app, the following error occurs: (SE-17080)

    {"error_description":"Invalid credentials","error":"invalid_client"}%

    When deploying the app, deployment fails with the following error: (SE-17119)

    Partition with name _defaultPersistentObjectStore does not exist in store

    To work around these issues, use the following clientStore configuration:

    <oauth2-provider:config
    	name="Oauth2_Provider_Config" doc:name="Oauth2 Provider Config"
    	doc:id="fbb2f727-5e7d-4cf5-8a84-52de678a017a" providerName="Mulesoft"
    	clientSecurityProvider="${myCompany.oauth.clientSecurityProvider}"
    	supportedGrantTypes="${myCompany.oauth.grantType}"
    	listenerConfig="api-httpListenerConfig" clientStore="Object_store">
  • A known issue with setting the TTL (time to live) value for an object store (SE-17454):

    Setting the value of entryTtl to 0 and the value of expirationInterval to less than or equal to 0 configures the TTL as 0 seconds (rather than the expected unlimited TTL). This behavior causes the object store entries to expire immediately and any operations that are dependent on the key in the app to fail.

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

4.2.1 Runtime Update

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

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

  • Fixed a problem in which a Mule application containing APIkit for SOAP and an Async scope did not start when launched from Runtime Manager. (SE-12193)

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

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

  • Resolved an issue in which MUnit tests did not run reliably in a Windows environment when started from the command line or Jenkins due to improper file cleanup. (MULE-17863/SE-13533)

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

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

  • Resolved an issue in which the Anypoint Connector for Kafka returned the java.nio.file.InvalidPathException: Illegal char <:> exception when accessing filesystem configuration files. (MULE-18569/SE-16282)

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

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

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

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

  • Fixed an issue in which an Object Store v2 exception appeared in the deployment log when starting applications that did not have Use Object Store v2 enabled. (SE-16728)

  • Upgraded the Object Store v2 plugin to version 4.0.27. (SE-13603/SE-10677/SE-16728)

Known Issues

The 4.2.1 release contains the following known issues with Object Store v2:

  • Two known issues when using OAuth2 authentication with an app with an object store:

    When sending a request to the app, the following error occurs: (SE-17080)

    {"error_description":"Invalid credentials","error":"invalid_client"}%

    When deploying the app, deployment fails with the following error: (SE-17119)

    Partition with name _defaultPersistentObjectStore does not exist in store

    To work around these issues, use the following clientStore configuration:

    <oauth2-provider:config
    	name="Oauth2_Provider_Config" doc:name="Oauth2 Provider Config"
    	doc:id="fbb2f727-5e7d-4cf5-8a84-52de678a017a" providerName="Mulesoft"
    	clientSecurityProvider="${myCompany.oauth.clientSecurityProvider}"
    	supportedGrantTypes="${myCompany.oauth.grantType}"
    	listenerConfig="api-httpListenerConfig" clientStore="Object_store">
  • A known issue with setting the TTL (time to live) value for an object store (SE-17454):

    Setting the value of entryTtl to 0 and the value of expirationInterval to less than or equal to 0 configures the TTL as 0 seconds (rather than the expected unlimited TTL). This behavior causes the object store entries to expire immediately and any operations that are dependent on the key in the app to fail.

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

4.2.0 Runtime Update

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

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

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

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

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

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

  • Resolved an issue in which the Anypoint Connector for Kafka returned the java.nio.file.InvalidPathException: Illegal char <:> exception when accessing filesystem configuration files. (MULE-18569/SE-16282)

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

  • Fixed an issue in which an application using more than one salesforce:replay-channel operation failed with status code 429. (SE-13603)

3.9.4 Runtime Update

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

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

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

3.9.3 Runtime Update

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

3.9.2 Runtime Update

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

3.9.1 Runtime Update

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

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

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

3.9.0 Runtime Update

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

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

3.8.7 Runtime Update

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

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

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

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

  • Updated to the latest operating system security patches.

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

  • Updated to the latest operating system security patches.

July 13, 2020

4.2.2 Runtime Update

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates in CloudHub Mule 4.x runtimes. (AGW-4199)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • Updated to the latest operating system security patches.

4.2.1 Runtime Update

  • Upgraded Object Store v2 plugin to 4.0.25.

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates in CloudHub Mule 4.x runtimes. (AGW-4199)

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

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

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

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

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

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

  • Updated to the latest operating system security patches.

Known Issue

The 4.2.1 release contains one known issue. (SE-16728)

The following Object Store v2 exception appears in the deployment log when starting applications that do not have Use Object Store v2 enabled:

Listener 'com.mulesoft.objectstore.cloud.internal.CloudObjectStoreListenerService' failed to process notification 'onArtifactCreated'

You can safely ignore the error. It has no impact on functionality.

July 9, 2020

4.3.0 Runtime Update

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • Updated to the latest operating system security patches.

4.2.0 Runtime Update

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates in CloudHub Mule 4.x runtimes. (AGW-4199)

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

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

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

  • Updated to the latest operating system security patches.

4.1.6 Runtime Update

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates in CloudHub Mule 4.x runtimes. (AGW-4199)

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

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

  • Updated to the latest operating system security patches.

4.1.5 Runtime Update

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates in CloudHub Mule 4.x runtimes. (AGW-4199)

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

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

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

  • Updated to the latest operating system security patches.

4.1.4 Runtime Update

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates in CloudHub Mule 4.x runtimes. (AGW-4199)

  • Updated to the latest operating system security patches.

4.1.3 Runtime Update

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates in CloudHub Mule 4.x runtimes. (AGW-4199)

  • Updated to the latest operating system security patches.

4.1.2 Runtime Update

  • Fixed an error when trying to access Gatekeeper and Analytics policy templates in CloudHub Mule 4.x runtimes. (AGW-4199)

  • Updated to the latest operating system security patches.

3.9.4 Runtime Update

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

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

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

  • Updated to the latest operating system security patches.

3.9.1 Runtime Update

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

  • Updated to the latest operating system security patches.

June 11, 2020

4.2.2 Runtime Update:

  • Security update.

June 9, 2020

4.2.x, 4.1.6, and 4.1.5 Runtime Updates:

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

June 2, 2020

4.3.0 Runtime Update:

  • Mule application threw the wrong HTTP response status code when api-gateway:autodiscovery was enabled. (SE-15935)

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

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

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

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

  • When an HTTP Listener is source of the flow, trying to reference a flow variable from the flow’s error response builder, the variable could not be found if a source policy was applied to the Listener. (MULE-18378)

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

  • Fixed an issue that might rarely cause a key collision with the ManagedCursorProvider cache. (MULE-18370)

  • MULE:OVERLOAD exception is thrown when first policy contains a Cache scope and second policy contains a Try scope error-handler. (MULE-18369)

  • Fixed a problem that prevented an application from starting after stopping using Runtime Manager. (MULE-18364)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • Fixed ObjectStoreToMapAdapter thrown exceptions when used or accessed concurrently. (MULE-18172)

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

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

  • Fixed an issue in which the Scheduler incorrectly ran twice. (SE-13691)

4.2.2 Runtime Update:

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

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

  • Resolved a problem with semantic versioning build-metadata when deploying an application. (SE-11087)

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

  • Fixed an issue where an exception affected class loading, even though the class exists in the dependencies using shared libraries. (SE-14245)

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

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

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

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

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

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

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

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

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

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

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

  • Fixed issues in which the Scheduler incorrectly ran twice or didn’t honor the configured cron or fixed-frequency setting on restart. (SE-13691)

4.2.1 Runtime Update:

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

  • Fixed issues in which the Scheduler incorrectly ran twice or didn’t honor the configured cron or fixed-frequency setting on restart. (SE-13691)

4.2.0 Runtime Update:

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

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

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

  • Resolved an unexpected state with the error handler org.mule.runtime.core.internal.event.EventContextDeepNestingException. (SE-15597)

  • Fixed issues in which the Scheduler incorrectly ran twice or didn’t honor the configured cron or fixed-frequency setting on restart. (SE-13691)

4.1.6 Runtime Update:

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

  • Fixed issues in which the Scheduler incorrectly ran twice or didn’t honor the configured cron or fixed-frequency setting on restart. (SE-13691)

4.1.5 Runtime Update:

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

  • Fixed issues in which the Scheduler incorrectly ran twice or didn’t honor the configured cron or fixed-frequency setting on restart. (SE-13691)

3.9.3 Runtime Update:

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

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

3.8.4 Runtime Update:

  • Fixed an java.util.concurrent.TimeoutException: Poll timeout expired issue when processing HTTP incoming application requests. (SE-13504)

All 3.8.x, 3.9.x, 4.1.x, and 4.2.x Runtime Update:

  • Updated to the latest operating system security patches.

May 5, 2020

4.3.0 Runtime Update:

  • Fixed an overload error that occurred when an API had a combination of two policies using caching and error-handler components. (MULE-18369)

All 3.8.x, 3.9.x, 4.1.x, and 4.2.x Runtime Update:

  • Updated to the latest operating system security patches.

April 20, 2020

4.2.x Runtime Update:

  • Fixed an issue that generated HTTP request timeouts in several connectors, including Salesforce Connector and Microsoft Dynamics Connector, which cause disruption in their operation. (SE-15659)

April 14, 2020

4.2.x Runtime Update:

  • Fixed an issue that, under high concurrency, might cause a leak in HTTP requests due to a race condition scenario. (SE-15540)

April 11, 2020

3.8.5 Runtime Update:

  • Fixed an issue with the RAML parser referencing other files using !include. (SE-15625)

April 10, 2020

4.2.1 Runtime Update:

  • Fixed a regression problem in Object Store v2 that was introduced with the April 7 update.

April 9, 2020

4.2.2 Runtime Update:

  • Fixed a regression problem in Object Store v2 that was introduced with the April 7 update.

April 7, 2020

All 4.x, 3.9.x, and 3.8.x Runtime Updates:

  • Set a new MetaspaceSize default to 128M so that it is possible to increase the metaspace memory and go beyond a more conservative threshold. This change is also introduced to maintain consistency with on-premises distributions.

  • Fixed issues to ensure RAML parser compatibility.

  • Targeted security fix.

April 4, 2020

4.2.2 Runtime Update:

  • Fixed an issue in the Salesforce connector where it did not automatically refresh the OAuth token, causing expired token errors interrupting execution of transactions with Salesforce. (SE-13371)

April 2, 2020

4.2.1 Runtime Update:

  • Fixed an issue in the Salesforce connector where it did not automatically refresh the OAuth token, causing expired token errors interrupting execution of transactions with Salesforce. (SE-13371)

  • Fixed an issue that affected the Web Service Consumer, causing long WSDL parsing times with multiple levels of nested imports. (SE-13634)

  • Fixed the error Failed to read geo directoryjava.nio.file.NoSuchFileException that appeared after deploying an application. (SE-14946)

March 30, 2020

4.2.2 Runtime Update:

  • Fixed an issue that caused StackOverflow errors in applications using the Database connector under heavy load. (SE-14663)

  • Fixed the error Failed to read geo directoryjava.nio.file.NoSuchFileException that appeared after deploying an application. (SE-14946)

March 29, 2020

All 3.8.x, 3.9.x, and 4.1.x Runtime Updates:

  • Fixed an issue with the RAML Parser.

  • Fixed the error Failed to read geo directoryjava.nio.file.NoSuchFileException that appeared after deploying an application. (SE-14946)

March 27, 2020

4.2.2 Runtime Update:

  • Updated the mule-http-ee-service dependency to version 1.5.3.

  • Fixed an OutOfMemory issue that occurred when Database Connector did not properly release heap memory when the request timed out. (SE-13982)

  • Fixed an issue in which an HTTP Request using NTLM authentication did not send the request payload resulting in a timeout request operation. (SE-13547)

March 25, 2020

4.2.1 Runtime Update:

  • Improved Object Store v2 initialization on CloudHub.

  • Improved usage of Object Store v2 by internal Mule 4 components.

  • Added support for fixed TTL in Object Store v2.

  • Fixed an issue in which an HTTP Request using NTLM authentication did not send the request payload resulting in a timeout request operation. (SE-13547)

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

March 18, 2020

All 3.8.x, 3.9.x, and 4.x Runtime Update:

  • Security fixes

3.9.0, 3.9.1, 3.9.2, and 3.9.3 Runtime Update:

  • Improved Object Store v2 initialization by Mule runtime engine.

March 16, 2020

4.2.2 Runtime Update:

  • Fixed an issue that caused empty FlowStack log messages.

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

  • Fixed an issue that affected the OAuth token refresh.

March 12, 2020

3.9.4 Runtime Update:

  • Fixed an issue that affected listener reconnection in the WMQ Connector.

  • Fixed an issue with DataWeave memory management. (SE-14927)

  • Improved Object Store v2 initialization by Mule runtime engine.

March 9, 2020

4.1.2, 4.1.3, 4.1.4, and 4.2.0 Runtime Update:

  • Reduced log levels for API gateway recoverable errors. (AGW-3949)

4.1.3, 4.1.4, 4.1.5, 4.1.6, 4.2.0, 4.2.1, and 4.2.2 Runtime Update:

  • Fixed an issue that caused unexpected behavior after a policy threw an unhandled exception during deployment.

4.2.0, 4.2.1, and 4.2.2 Runtime Update:

  • Fixed an issue in which an HTTP Request using NTLM authentication did not send the request payload resulting in a timeout request operation. (SE-13547)

4.2.0 and 4.2.2 Runtime Update:

  • Fixed an issue that affected the Web Service Consumer, causing long WSDL parsing times with multiple levels of nested imports. (SE-13634)

4.1.4 Runtime Update:

  • Fixed an issue in which a DataWeave expression used to display information with the Logger component failed in high-load scenarios. (SE-10706)

3.8.6 Runtime Update:

  • Fixed an issue that caused validation errors in the API console.

March 6, 2020

3.8.7 Runtime Update:

  • Fixed an issue that caused thread-related exceptions.

March 3, 2020

4.1.2 and 4.1.5 Runtime Update:

  • Fixed a policy violation issue that was introduced with the previous runtime version update.

3.8.2 and 3.8.7 Runtime Update:

  • Improved Object Store v2 initialization by Mule runtime engine.

February 27, 2020

4.1.2 Runtime Update:

  • Fixed an issue that caused unexpected behavior after a policy threw an unhandled exception during deployment.

  • Fixed an issue that resulted in a FileNotFoundException error while executing a DataWeave expression in large-batch scenarios, which was caused by prematurely closing the content stream. (SE-9379)

3.8.3, 3.8.5, and 3.8.6 Runtime Update:

  • Improved Object Store v2 initialization by Mule runtime engine.

February 26, 2020

3.8.0 and 3.8.1 Runtime Update:

  • Improved Object Store v2 initialization by Mule runtime engine.

February 20, 2020

4.2.0, 4.2.1, and 4.2.2 Runtime Update:

  • Fixed an issue in which batch records didn’t process when the Persistent queues option was enabled. (SE-13300)

4.1.5, 4.1.6, 4.2.1, and 4.2.2 Runtime Update:

  • Reduced log levels for API Gateway recoverable errors. (AGW-3949)

4.2.0 Runtime Update:

  • Fixed inconsistent DataWeave transformations called via a SOAP router when executed across Linux and Windows operating systems. [SE-11664]

3.9.4 Runtime Update:

  • Added a system property to avoid removing the object store folder on disposal. (SE-14361)

3.9.3 and 3.9.4 Runtime Update:

  • Monitoring enhancements

February 14, 2020

4.1.5, 4.1.6, 4.2.1, and 4.2.2 Runtime Update:

  • Added support for HTTP header injection in Anypoint Connector for HTTP. (MULE-17706)

4.2.1 Runtime Update:

  • Fixed an issue in which the refresh dance did not execute after the access token expired. (MULE-17812)

3.9.1 and 3.9.2 Runtime Update:

  • Fixed an issue in which special characters were corrupt in the Content-Disposition header. (SE-13575)

3.8.7 Runtime Update:

  • Added a system property to avoid removing the object store folder on disposal. (SE-14361)

February 13, 2020

4.1.5, 4.1.6, 4.2.1, and 4.2.2 Runtime Update:

  • Monitoring enhancements

4.2.2 Runtime Update:

  • Fixed leak problem when processing large payloads in DataWeave function calls from MEL similar to #[dw(…​)] that generate temporary files like /tmp/dw-buffer*.tmp. (SE-14421)

  • Fixed dw::core::Strings::substringAfterLast function not working as expected. (SE-14808)

February 11, 2020

3.9.4 Runtime Update:

  • Fixed an issue with the RAML console and API proxies. (SE-13029)

  • Fixed an issue with OAuth authentication. (MULE-17688)

  • Fixed issues with DataWeave transformations. (SE-14020, SE-14371, SE-14423)

4.2.1 and 4.2.2 Runtime Update:

  • Fixed an issue in which the refresh dance did not execute after the access token expired. (MULE-17812)

  • Fixed an issue in which Mule apps did not process more than one message from Anypoint MQ. (SE-14595)

4.2.2 Runtime Update:

  • The toBase64 and fromBase64 functions now behave the same way as in version 4.2.1. (SE-14606)

  • DataWeave fixes for union and enum types in Avro schemas. (SE-14561 and SE-14625)

February 10, 2020

4.1.1, 4.1.2, 4.1.3, 4.1.4, 4.1.5, and 4.1.6 Runtime Update:

  • Security fixes

February 4, 2020

3.8.7, 3.9.0, 3.9.1, 3.9.2, 3.9.3, and 3.9.4 Runtime Update:

  • Security fixes

3.9.0 Runtime Update:

  • Improved Object Store v2 initialization by Mule runtime engine.

February 3, 2020

4.2.0, 4.2.1, and 4.2.2 Runtime Update:

  • Security fixes

January 22, 2020

3.8.7 Runtime Update:

  • Reverted the January 10 patch that addressed SE-5737.

January 10, 2020

4.2.2 Runtime Update:

  • Updated with latest OS security patches.

3.8.0, 3.8.1, 3.8.2, 3.8.3, 3.8.4, 3.8.5, 3.8.6, 3.8.7, 3.9.0, 3.9.1, 3.9.2, 4.1.1, 4.1.2, 4.1.3, 4.1.4, 4.1.5, 4.1.6, 4.2.0, and 4.2.1 Runtime Update:

  • Fixed an issue where AdoptJdk was shown as an unsupported vendor.

  • Updated with latest OS security patches.

3.9.3 and 3.9.4 Runtime Update:

  • Fix an issue where special characters were corrupted in the Content-Disposition header fileName attribute. (SE-14283)

  • Fixed an issue where AdoptJdk was shown as an unsupported vendor.

  • Updated with latest OS security patches.

3.8.7 Runtime Update:

  • Fixed an issue where illegal access to an event from a non-corresponding thread resulted in a java.lang.IllegalStateException: Only owner thread can write to message error. (SE-5737)

3.8.4 Runtime Update:

  • Improved Object Store v2 initialization by Mule runtime engine.

January 9, 2020

4.2.1 and 4.2.2 Runtime Update:

  • Fixed an issue where the API gateway was using the Business Group organization ID instead of the Master organization ID for OAuth provider operations. (SE-13786)

December 24, 2019

3.8.4 and 3.8.6 Runtime Update:

  • CloudHub Mule worker-reliability enhancements and performance improvements

December 16, 2019

4.2.1 Runtime Update:

  • Fixed a DataWeave OOM error Direct buffer memory in 0.1 worker. (SE-13951)

December 13, 2019

4.2.2 Runtime Update:

  • Fixed a DataWeave OOM error Direct buffer memory in 0.1 worker. (SE-13951)

3.9.3 Runtime Update:

  • Fixed an issue in which special characters were corrupt in the Content-Disposition header. (SE-13575)

December 12, 2019

3.9.3 and 3.9.4 Runtime Update:

  • Fixed an issue where Anypoint Monitoring didn’t show inbound metrics. (SE-13726)

  • Fixed an issue where the Anypoint Monitoring agent was blocking threads. (SE-14121)

December 10, 2019

3.8.0, 3.8.1, 3.8.2, 3.8.3, 3.8.4, 3.8.5, 3.8.6, 3.8.7, 3.9.0, 3.9.1, 3.9.2, 3.9.3, 3.9.4, 4.1.1, 4.1.2, 4.1.3, 4.1.4, 4.1.5, 4.1.6, 4.2.0, 4.2.1, and 4.2.2 Runtime Update:

  • Updated with latest OS and security patches.

3.8.5 Runtime Update:

  • Fixed an issue where the API console for CloudHub applications generated RAML parsing errors. [SE-13887]

  • Fixed an issue where the Mule monitor failed to recover an unresponsive Mule process. [SE-14096]

4.2.1 Runtime Update:

  • Fixed an issue that caused a MULE:FLOW_BACK_PRESSURE error in 4.2.x. [SE-13832]

  • Fixed an Out of Memory issue in Batch Aggregator. [SE-13440]

4.2.0 Runtime Update:

  • Fixed an issue that caused a MULE:FLOW_BACK_PRESSURE error in 4.2.x. [SE-13832]

3.9.3 Runtime Update:

  • Fixed an issue in which special characters were corrupt in the Content-Disposition header. (SE-13575)

December 4, 2019

3.8.6 Runtime Update:

  • Fixed an issue where the Mule monitor failed to recover an unresponsive Mule process. [SE-14096]

December 2, 2019

3.9.3 Runtime Update:

  • Fixed an issue where API Kit failed to validate yyyy-m-d and yyyy-m-dThh:mi:ss date formats. [SE-12947]

  • Fixed an issue where the monitoring feature didn’t work on workers with a static IP address. [SE-13729]

November 29, 2019

4.2.1 and 4.2.0 Runtime Update:

  • Fixed an issue where the configuration property output not correct when the prefix was escaped. [SE-13196]

3.9.1 Runtime Update:

  • Fixed an issue where the monitoring feature didn’t work on workers with a static IP address. [SE-13729]

November 25, 2019

4.1.6 and 4.2.1 Runtime Update:

  • Fixed an issue where the monitoring feature didn’t work on workers with a static IP address. [SE-13729]

November 21, 2019

4.1.5 Runtime Update:

  • Fixed a NullPointerException that occurred with patch SE-12807-4.2.1-1.0 applied. [SE-13580]

  • Fixed an issue where the monitoring feature didn’t work on workers with a static IP address. [SE-13729]

4.2.0 Runtime Update:

  • Performance assessment for WS consumer when using explicit custom-transport-configuration [SE-10687]

  • Fixed an issue where the monitoring feature didn’t work on workers with a static IP address. [SE-13729]

November 14, 2019

3.9.2 Runtime Update:

  • Fixed an issue where the monitoring feature didn’t work on workers with a static IP address. [SE-13729]

November 12, 2019

4.2.1 Runtime Update:

  • Flow backpressure check is now performed before source policies are applied. [MULE-16513]

November 7, 2019

3.9.3 Runtime Update:

  • RAML console now works on CloudHub proxy. [SE-13029]

November 6, 2019

3.8.6, 3.8.7, 3.9.0, 3.9.1, 3.9.2, 3.9.3, 4.1.2, 4.1.3, 4.1.4, 4.1.5, 4.1.6, 4.2.0, and 4.2.1 Runtime Update:

  • Fixed an issue with persistent queues in the Europe control plane [SE-13657]

  • Fixed a backward-compatibility issue with TLS support. [SE-13613]

October 31, 2019

4.1.6 Runtime Update:

  • Fixed the KryoException (Could not deserialize object) error [SE-13124]

4.1.5 Runtime Update:

  • Fixed an issue in which overriding encrypted properties failed when referenced from within a properties file in datasource definition [SE-13494]

  • Fixed the KryoException (Could not deserialize object) error [SE-13124]

October 30, 2019

4.2.1 Runtime Update:

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

  • Fixed an issue in which Mule request was not being processed intermittently, even though the request was received by the Listener [SE-13677]

  • Fixed an issue with the splitBy function failing with the error Caused by: java.io.IOException: Stream is closed when running without debugging mode [SE-12836]

  • Fixed error HTTP Packet header is too large [SE-13213]

  • Added the port where HTTP listens to logs [SE-13099]

  • Fixed an issue where the ListenerConfig attribute of <oauth2-provider:config> was not working when referencing domain project listener [SE-11990]

  • Fixed an issue with filenames in UTF-8 where the £ character in a multipar/form-data was transformed to £ in ASCII [SE-9292]

  • Fixed an issue that caused a NullPointerException error with patch SE-12807-4.2.1-1.0 applied [SE-13580]

  • Fixed an issue where Try Scope with On Error Continue stops and does not continue processing [SE-13184]

  • Fixed an issue with configuration property values that include special characters [SE-13196]

4.2.0 Runtime Update:

  • Fixed an issue in which Mule request was not being processed intermittently, even though the request was received by the Listener [SE-13677]

  • Fixed an issue with the splitBy function failing with the error Caused by: java.io.IOException: Stream is closed when running without debugging mode [SE-12836]

  • Fixed an issue that caused a NullPointerException error with patch SE-12807-4.2.1-1.0 applied [SE-13580]

  • Fixed an issue with configuration property values that include special characters [SE-13196]

  • Fixed a JMS connector configuration error [SE-11912]

October 24, 2019

3.9.0, 3.9.1 and 3.8.7 Runtime Update:

  • Fixed the org.glassfish.grizzly.connectionpool.Endpoint.connect and java.lang.AbstractMethodError errors with the 3.9.1 patch release (10-22-2019). [SE-13669]

3.8.7 Runtime Update:

  • Fixed an issue when insecure TLS TrustStore was used, the patch release SE-12252 caused NoSuchMethodError exception error in CloudHub, which prevented applications from being deployed. [SE-13615]

October 23, 2019

4.2.1 and 4.2.0 Runtime Update:

  • Fixed an issue that caused Mule runtime engine to throw exception java.lang.NoSuchMethodError: org.mule.runtime.extension.api.runtime.config.ConfigurationStats.getRunningSources(). [SE-13611]

October 22, 2019

4.2.1 Runtime Update:

  • Fixed an issue where a CloudHub patch release caused an error: [SE-13612]

    java.lang.NoSuchMethodError: org.mule.runtime.core.internal.util.rx.ConditionalExecutorServiceDecorator.<init>(Lorg/mule/runtime/api/scheduler/Scheduler;Ljava/util/function/Predicate;)V

3.9.x Runtime Updates:

  • Fixed java.util.concurrent.TimeoutException: Poll timeout expired issue. [SE-13504]

  • Fixed an issue when insecure TLS TrustStore was used, the patch release SE-12252 caused NoSuchMethodError exception error in CloudHub, which prevented applications from being deployed. [SE-13615]

October 16, 2019

4.2.1 Runtime Update:

  • Fixed an issue where the HTTP request did not renegotiate NTLM authentication when new credentials were provided [SE-11204]

  • Fixed a leak in the first classloader that invokes an HTTP service in the Mule app. [EE-6968]

4.2.0 Runtime Update:

  • Fixed an issue where the JWT policy was not responding under load when the CPU_INTENSIVE operation was present in the application. [SE-13091]

  • SFTP Connector now reconnects after a JSchException error. [SE-12626]

  • Fixed an issue where the CloudHub worker was unresponsive and unable to start on its own. [SE-13004]

  • Fixed an issue with excessive logging filling /tmp and partition 100%. [SE-12896]

  • Fixed 100% CPU usage issue due to HTS service. [SE-13388]

  • Fixed inconsistent property loading. [SE-13118]

  • Fixed an issue where the HTTP request did not renegotiate NTLM authentication when new credentials were provided [SE-11204]

  • Fixed a leak in the first classloader that invokes an HTTP service in the Mule app. [EE-6968]

4.1.5 Runtime Update:

  • HTTP Request Connector was not honoring the queryParameter order. [SE-11445]

  • SFTP Connector was not reconnecting after JSchException error. [SE-12626]

  • Fixed an issue where the CloudHub worker was unresponsive and unable to start on its own. [SE-13004]

  • Fixed an issue with excessive logging filling /tmp and partition 100%. [SE-12896]

  • Fixed 100% CPU usage issue due to HTS service. [SE-13388]

  • Fixed inconsistent property loading. [SE-13118]

4.1.2, 4.1.3 and 4.1.4 Runtime Updates:

  • SFTP connector was not reconnecting after JSchException error. [SE-12626]

  • Fixed an issue where the CloudHub worker was unresponsive and unable to start on its own. [SE-13004]

  • Fixed an issue with excessive logging filling /tmp and partition 100%. [SE-12896]

  • Fixed 100% CPU usage issue due to HTS service. [SE-13388]

  • Fixed inconsistent property loading. [SE-13118]

3.9.1 and 3.8.7 Runtime Updates:

  • Fixed an issue where the CloudHub worker was unresponsive and unable to start on its own. [SE-13004]

  • Fixed an issue with excessive logging filling /tmp and partition 100%. [SE-12896]

  • Fixed 100% CPU usage issue due to HTS service. [SE-13388]

  • Fixed inconsistent property loading. [SE-13118]

3.9.3 Runtime Updates:

  • Fixed an issue with CloudHub Mule runtime engine 3.9.3 AMI using an evaluation license. [SE-13525]

October 15, 2019

4.2.1 Runtime Update:

  • Fixed an issue where the JWT policy was not responding under load when the CPU_INTENSIVE operation was present in the application. [SE-13091]

  • Inbound metrics did not appear for some apps. [SE-13095]

  • Fixed an issue where the CloudHub worker was unresponsive and unable to start on its own. [SE-13004]

  • Fixed an issue with excessive logging filling /tmp and partition 100%. [SE-12896]

  • Fixed 100% CPU usage issue due to HTS service. [SE-13388]

  • Fixed inconsistent property loading. [SE-13118]

  • SFTP connector was not reconnecting after JSchException error. [SE-12626]

4.1.6 Runtime Update:

  • Inbound metrics did not appear for some apps. [SE-13095]

  • Fixed an issue where the CloudHub worker was unresponsive and unable to start on its own. [SE-13004]

  • Fixed an issue with excessive logging filling /tmp and partition 100%. [SE-12896]

  • Fixed an issue where the HTS service was not deleting file descriptors. [SE-13388]

  • Fixed inconsistent property loading. [SE-13118]

  • SFTP connector was not reconnecting after JSchException error. [SE-12626]

October 9, 2019

3.9.3 Runtime Updates:

  • Inbound metrics do not appear for some apps. [SE-13095]

September 20, 2019

4.1.6 Runtime Update:

  • Mule app encounters deadlock when submitting parallel requests in CloudHub. [SE-13047]

  • Fixed memory leak on PolicyStateHandler for error scenarios. [SE-12906]

4.1.5 Runtime Update:

  • FTPS connector is not reusing connection from the pool. [SE-12776]

  • A nonexistent file path causes SFTP "Connection pool is exhausted" error. [SE-12279]

4.1.4 and 4.2.0 Runtime Updates:

  • A nonexistent file path causes SFTP "Connection pool is exhausted" error. [SE-12279]

3.9.0, 3.9.1, 3.9.2, and 3.9.3 Runtime Update:

  • Update CloudHub AMI with new version of July 2019 security patch. [SE-13138]

September 16, 2019

3.8.7 Runtime Update:

  • CloudHub Mule worker-reliability enhancements and performance improvements

September 9, 2019

4.1.5 Runtime Update:

  • Deadlock when submitting parallel requests. [SE-13047]

  • Inbound metrics do not appear for app. [SE-13095]

  • Fix memory leak on PolicyStateHandler for error scenarios [SE-12906]

3.9.3, 4.1.1, 4.1.2, 4.1.3, 4.1.5, and 4.2.0 Runtime Update:

  • Inbound metrics do not appear for app. [SE-13095]

September 5, 2019

4.2.0 Runtime Update:

  • Sinks must be used by only one thread when running a transaction. [MULE-16936]

3.9.0 Runtime Update:

  • APIKit incorrectly overrides the default transformation graph. [SE-7162]

All 3.8.x Runtime Updates:

  • If defaultCipherSuites isn’t specified, all cipher suites supported by enabled protocols are used. [SE-12252]

September 4, 2019

All 4.2.x Runtime Updates:

  • CloudHub Mule worker-reliability enhancements and performance improvements for 1 vCore

  • CloudHub Mule workers now include Correlation ID in log messages.

All 4.1.x Runtime Updates:

  • CloudHub Mule worker-reliability enhancements and performance improvements for 1 vCore

  • CloudHub Mule workers now include Correlation ID in log messages.

All 3.9.x Runtime Updates:

  • CloudHub Mule worker-reliability enhancements and performance improvements for 1 vCore

September 3, 2019

4.2.1 Runtime Update:

  • SFTP with public key authentication fails after 5 minutes. [SE-11329]

  • SFTP listener with identity file and start delay set as 0 fails to retrieve file. [SE-11198]

  • CloudHub Mule worker-reliability enhancements and performance improvements for 0.2 vCore

4.2.0 Runtime Update:

  • High CPU when using VM listener with persistent queue even when the app is idle. [SE-11994]

  • SFTP with public key authentication fails after 5 minutes. [SE-11329]

  • SFTP listener with identity file and start delay set to 0 fails to retrieve file. [SE-11198]

  • CloudHub Mule worker-reliability enhancements and performance improvements for 0.2 vCore

All 4.1.x Runtime Updates:

  • CloudHub Mule worker-reliability enhancements and performance improvements for 0.2 vCore

All 3.9.x Runtime Updates:

  • CloudHub Mule worker-reliability enhancements and performance improvements for 0.2 vCore

August 30, 2019

4.2.1 Runtime Update:

  • Anypoint Visualizer is not showing inbound connections. [SE-12476]

  • Inbound Metrics are missing for app in Anypoint Monitoring. [SE-12832]

  • High CPU - When using VM listener with persistent queue even when the app is idle. [SE-11994]

3.8.7, 3.9.3, and 4.1.5 Runtime Update:

  • Anypoint Visualizer is not showing inbound connections. [SE-12476]

  • Inbound Metrics are missing for app in Anypoint Monitoring. [SE-12832]

August 28, 2019

4.2.1 Runtime Update:

  • Address incomplete fix for SE-12772.

4.2.0 Runtime Update:

  • Try scope with transactions forces all components to execute on CPU_LITE threads. [SE-12772]

  • Cannot open a new cursor on a closed stream inside a Foreach scope. [SE-12807]

August 27, 2019

4.2.1 Runtime Update:

  • Try scope with transactions forces all components to execute on CPU_LITE threads. [SE-12772]

  • Cannot open a new cursor on a closed stream inside a for-each scope. [SE-12807]

  • SFTP connection pool is exhausted when file path does not exist. [SE-12279]

  • Resolved a problem in which the Cache scope fails validation when the payload is empty when entering the scope. [SE-12743]

4.1.5 Runtime Update:

  • Try scope with transactions forces all components to execute on CPU_LITE threads. [SE-12772]

  • Cannot open a new cursor on a closed stream inside a for-each scope. [SE-12807]

4.1.4 Runtime Update:

  • Try scope with transactions forces all components to execute on CPU_LITE threads. [SE-12772]

All 3.9.x Runtime Updates:

  • CloudHub Mule worker-reliability enhancements and performance improvements for 0.1 vCore

August 23, 2019

4.2.0 and 4.2.1 Runtime Update:

  • CloudHub Mule worker-reliability enhancements and performance improvements for 0.1 vCore

August 22, 2019

4.1.1, 4.1.2, 4.1.3, 4.1.4, and 4.1.5 Runtime Update:

  • CloudHub Mule worker-reliability enhancements and performance improvements for 0.1 vCore

August 14, 2019

3.9.0 Runtime Update:

  • NoSuchMethodError on APIKit after latest update [SE-12795]

3.8.7 Runtime Update:

  • Add new Visualizer and Monitoring capabilities

  • Fix Threat Protection Policies showing internal class names when an invalid XML or JSON payload are sent. [SE-12389]

3.8.6 Runtime Update:

  • Fix Threat Protection Policies showing internal class names when an invalid XML or JSON payload are sent. [SE-12389]

3.8.5 Runtime Update:

  • Fix Threat Protection Policies showing internal class names when an invalid XML or JSON payload are sent. [SE-12389]

August 9, 2019

3.9.3 Runtime Update:

  • Empty X-MULE-DDOS-VIOLATION header reaching backend. [SE-12611]

August 8, 2019

4.2.0 and 4.2.1 Runtime Update:

  • Out of Memory in Metaspace when redeploying application. [SE-10506]

  • Spring dependency collision between runtime and connectors. [SE-12204]

  • Flow Backpressure error when running DataWeave transformation. [SE-12583]

  • Extensions configuration being leaked over time. [SE-12495]

  • Update OSv2 plugin to version 4.0.22 using POST method instead of PUT for store requests. [SE-11308]

  • OAuth Module for HTTP Requester is leaking threads. [SE-12028]

  • Unlabelled endpoint is shown within the Monitoring dashboard. [SE-12397]

4.1.5 Runtime Update:

  • IllegalStateException on batch job with concurrency. [SE-12451]

August 7, 2019

4.1.5 Runtime Update:

  • Fixed inconsistent DataWeave transformations called via a SOAP router when executed across Linux and Windows operating systems. [SE-11664]

  • Strings with special characters are not being logged correctly. [SE-12345]

  • Out of Memory in Metaspace when redeploying application. [SE-10506]

  • Extensions configuration being leaked over time. [SE-12495]

  • Update OSv2 plugin to version 4.0.22 using POST method instead of PUT for store requests. [SE-11308]

  • OAuth Module for HTTP Requester is leaking threads. [SE-12028]

  • Unlabelled endpoint is shown within the Monitoring dashboard. [SE-12397]

4.1.4 Runtime Update:

  • OAuth Module for HTTP Requester is leaking threads. [SE-12028]

  • Fix scheduling issue when using OAuth2 policies. [SE-10874]

  • Unlabelled endpoint is shown within the Monitoring dashboard. [SE-12397]

3.9.3, 3.9.2 Runtime Updates:

  • Maximum attribute size limit exceeded when parsing XML using Object to XML transformer. [SE-11752]

  • Maximum attribute size limit exceeded when parsing XML using DataWeave. [SE-11914]

All 3.9.x Runtime Updates:

  • Fix Threat Protection Policies showing internal class names when an invalid XML or JSON payload are sent. [SE-12389]

  • SSL cipher suites list changed with latest patch of 3.9.0 and 3.9.1 in CloudHub. [SE-12252]

  • Analytics collector does not allow to access the message. [SE-12446]

July 16, 2019

4.2.0 Runtime Update:

  • IllegalStateException on batch job with concurrency. [SE-12451]

  • Faster application deployment with Monitoring feature disabled.

4.1.5 Runtime Update:

  • Faster application deployment with Monitoring feature disabled.

3.9.3 Runtime Update:

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

  • Faster application deployment with Monitoring feature disabled.

July 12, 2019

3.9.2 and 3.9.3 Runtime Update:

  • Address incomplete fix for SE-11195 (Error loading System Properties).

July 11, 2019

4.2.0 Runtime Update:

  • PipelineMessageNotificationListener returns a PipelineMessageNotification with null event when an exception is raised in the Mule flow. [MULE-17081]

  • org.springframework.beans.factory.support.NullBean cannot be cast. [SE-12247]

  • FlowRef component inside an on-error scope causes duplicate chain execution. [SE-12017]

3.9.2 and 3.9.3 Runtime Update:

  • Error loading System Properties. [SE-11195]

June 27, 2019

4.2.0 Runtime Update:

  • Update scheduler pool configuration in design environment.

3.8.7, 3.8.6, 3.8.5, 3.8.4, 3.8.2, 3.8.1 and 3.8. Runtime Update:

  • Switched from OracleJDK 8 to OpenJDK 8.

June 26, 2019

4.1.5 Runtime Update:

  • IBM MQ listener receiving REPLY_TO queue header message unable to reconnect after the queue manager restarts. [SE-11261]

June 19, 2019

4.1.5 Runtime Update:

  • Improved memory consumption in Monitoring data path

June 12, 2019

4.2.0, 4.1.5, 4.1.4, 4.1.3, 4.1.2 and 4.1.1 Runtime Update:

  • NullPointerException when running Mule applications with batches and persistent queues enabled in CloudHub. [SE-11599]

June 7, 2019

4.1.5 Runtime Update:

  • Batch job corrupted when debugging app [SE-9826]

3.9.1 and 3.9.2 Runtime Update:

  • JSON validation fails with the error: error: object instance has properties which are not allowed by the schema: [SE-11753]

June 5, 2019

4.1.5, 4.1.4, 4.1.3, 4.1.2 and 4.1.1 Runtime Update:

  • Switched from OracleJDK 8 to OpenJDK 8

June 4, 2019

4.1.4, 4.1.5 and 4.2.0 Runtime Update:

  • Fix custom policies reusing class loader between versions. [SE-12023]

  • Fix class loading isolation issues when initializing apps. [SE-11887]

4.1.1, 4.1.2, 4.1.3, 4.1.4 and 4.1.5 Runtime Update:

  • Fix policy violations not being sent when caused by an automated policy.

May 28, 2019

4.2.0 Runtime Update:

  • APIKit validation error issue after version 1.1.9 [SE-11839]

  • Sporadic NullPointerException in Grizzly ClientHttpResponseImpl.getProcessingState() [SE-8085]

  • Accept-Expression in Batch job not evaluated correctly [SE-11666]

  • JMS consumer stops consuming messages after the stop/start flow operation [SE-11450]

  • Removed unexpected warnings and errors related to file system permissions in logs when using secure properties [SE-7975]

4.1.5 Runtime Update:

  • Sporadic NullPointerException in Grizzly ClientHttpResponseImpl.getProcessingState() [SE-8085]

  • Accept-Expression in Batch job not evaluated correctly [SE-11666]

  • JMS consumer stops consuming messages after the stop/start flow operation [SE-11450]

3.9.2, 3.9.1 and 3.9.0 Runtime Update:

  • Removed unexpected warnings and errors related to file system permissions in logs when using secure properties [SE-7975]

May 24, 2019

4.1.5 and 4.2.0 Runtime Update:

  • Visualizer properties not picked up from the mule-app.properties file [SE-10374]

3.9.2 Runtime Update:

  • Address incomplete fix in OAuth service [SE-10423]

  • Visualizer properties not picked up from the mule-app.properties file [SE-10374]

3.9.1 Runtime Update:

  • Address incomplete fix in OAuth service [SE-10423]

  • Thread leak after redeployment when using OAuth client credentials [SE-10217]

May 22, 2019

3.9.2 Runtime Update:

  • Switched from OracleJDK 8 to OpenJDK 8

  • Address incomplete fix in RAML parser [SE-11926]

3.9.1 Runtime Update:

  • Switched from OracleJDK 8 to OpenJDK 8

  • Address incomplete fix in RAML parser [SE-11926]

3.9.0 Runtime Update:

  • Switched from OracleJDK 8 to OpenJDK 8

May 21, 2019

3.9.1 Runtime Update:

  • Address incomplete fix in RAML parser [SE-10737]

May 16, 2019

3.8.7 Runtime Update:

  • FTP connector not closing connections properly when server closes the socket. [SE-11688]

May 14, 2019

4.2.0 Runtime Update:

  • Persistent queues not working for batch and vm:publish-consume operation. [SE-11698, SE-11599, SE-10583]

4.1.1, 4.1.2, 4.1.3, 4.1.4 and 4.1.5 Runtimes Update:

  • Persistent queues not working for batch and vm:publish-consume operation. [SE-11698, SE-11599, SE-10583]

May 8, 2019

4.2.0 Runtime Update:

  • Streaming a large payload through HTTP generates a timeout [SE-10129]

May 2, 2019

4.2.0 Initial Release:

  • Mule 4.2 runs on CloudHub using AdoptOpenJDK 1.8 instead of Oracle JDK.

  • There is an important update included for the API Caching Policy. See the HTTP Caching Release Notes for more information.

  • For information about changes and improvements in the Mule 4.2.0 runtime, see Mule Runtime 4.2.0 Release Notes.

April 26, 2019

4.1.2-4.1.4 Runtime Update:

  • Fix NullPointerException reported in the logs by some connectors when the Monitoring feature is enabled. [SE-11483]

3.9.2 Runtime Update:

  • Address incomplete fix in RAML parser [SE-10737]

  • Ping flow flooding Insight when metadata is enabled and auto restart is set for CloudHub applications [SE-11327]

3.9.1 Runtime Update:

  • Address incomplete fix in RAML parser [SE-10737]

  • Ping flow flooding Insight when metadata is enabled and auto restart is set for CloudHub applications [SE-11327]

3.9.0 Runtime Update:

  • Fix NullPointerException reported in the logs by some connectors when the Monitoring feature is enabled. [SE-11483]

  • Some inbound request failures are not taken into account in Monitoring dashboards. [SE-10544]

  • Visualizer properties are not picked up from the mule-app.properties file. [SE-10374]

  • Ping flow flooding Insight when metadata is enabled and auto restart is set for CloudHub applications [SE-11327]

April 25, 2019

4.1.5 Runtime Update:

  • HTTP Listener discloses full URL in error response. [SE-10302]

  • Fix NullPointerException reported in the logs by some connectors when the Monitoring feature is enabled. [SE-11483]

3.9.2 Runtime Update:

  • RAML with date-only/datetime-only fails to parse in APIKit. [SE-10737]

  • String interpolation in logger component fails on debug mode. [SE-11094]

  • Login screen in API Console disappears. [SE-8445]

  • Fix NullPointerException reported in the logs by some connectors when the Monitoring feature is enabled. [SE-11483]

  • Some inbound request failures are not taken into account in Monitoring dashboards. [SE-10544]

  • Visualizer properties are not picked up from the mule-app.properties file. [SE-10374]

3.9.1 Runtime Update:

  • RAML with date-only/datetime-only fails to parse in APIKit. [SE-10737]

  • String interpolation in logger component fails on debug mode. [SE-11094]

  • Login screen in API Console disappears. [SE-8445]

  • Fix NullPointerException reported in the logs by some connectors when the Monitoring feature is enabled. [SE-11483]

  • Some inbound request failures are not taken into account in Monitoring dashboards. [SE-10544]

  • Visualizer properties are not picked up from the mule-app.properties file. [SE-10374]

April 8, 2019

4.1.5 Runtime Update:

  • Unclosed stream causes memory leak in foreach loop [SE-11390]

  • Degraded performance when using a Custom Transport Configuration in Web Service Consumer [SE-10687]

  • Fixed an issue that resulted in a FileNotFoundException error while executing a DataWeave expression in large-batch scenarios, which was caused by prematurely closing the content stream. (SE-9379)

  • Fixed an issue in which a DataWeave expression used to display information via the Logger component failed on high load scenarios. [SE-10706]

3.9.2 Runtime Update:

  • MEL variable returns null instead of actual value [SE-11479]

3.9.1 Runtime Update:

  • MEL variable returns null instead of actual value [SE-11479]

3.9.0 Runtime Update:

  • Both Visualizer and Monitoring functionality are now controlled through the Anypoint Monitoring UI. After you upgrade to this runtime, your apps no longer appear in Visualizer. The apps are still there, but you need to re-enable Visualizer functionality in the Anypoint Monitoring Settings to see them. For more information, see Enable Monitoring for Mule Apps Deployed to CloudHub.

April 5, 2019

3.9.1 Runtime Update:

  • Both Visualizer and Monitoring functionality are now controlled through the Anypoint Monitoring UI. After you upgrade to this runtime, your apps no longer appear in Visualizer. The apps are still there, but you need to re-enable Visualizer functionality in the Anypoint Monitoring Settings to see them. For more information, see Enable Monitoring for Mule Apps Deployed to CloudHub.

April 4, 2019

3.9.2 Runtime Update:

  • Both Visualizer and Monitoring functionality are now controlled through the Anypoint Monitoring UI. After you upgrade to this runtime, your apps no longer appear in Visualizer. The apps are still there, but you need to re-enable Visualizer functionality in the Anypoint Monitoring Settings to see them. For more information, see Enable Monitoring for Mule Apps Deployed to CloudHub.

March 26, 2019

3.8.7 Runtime Update:

  • SFTP connector is not closing connections [SE-10977]

  • Throttling policy doesn’t clean its cache [SE-10534]

3.8.6 Runtime Update:

  • Throttling policy doesn’t clean its cache [SE-10534]

3.8.4 Runtime Update:

  • Added alerting in case disk usage exceeds threshold [SE-11147]

March 25, 2019

3.9.2 Runtime Update:

  • Oracle type with CLOB field raises error [SE-10726]

  • Database connector file descriptor leaks when processing large payloads [SE-11071]

  • SFTP connector is not closing connections [SE-10977]

  • Throttling policy doesn’t clean its cache [SE-10534]

3.9.1 Runtime Update:

  • Oracle type with CLOB field raises error [SE-10726]

  • Database connector file descriptor leaks when processing large payloads [SE-11071]

March 22, 2019

4.1.1, 4.1.2, 4.1.3, 4.1.4 and 4.1.5 Runtimes Update:

  • Visualizer and Monitoring functionality are part of these CloudHub runtimes now, so there is no need to use separate 4.1.x-AM runtimes any longer.

  • Both Visualizer and Monitoring functionality are now controlled through the Anypoint Monitoring UI. After you upgrade to Mule 4.1.x you will no longer see your apps in Visualizer. They are still there, but you need to re-enable Visualizer functionality in the Anypoint Monitoring Settings. For more information, see enable the Anypoint Monitoring agent.

This release contains the following known issue:

SE-11007: Do not enable advanced app log functionality on 0.1 VCore configurations.

Workaround: Use 0.2 VCore or higher configurations.

March 21, 2019

3.8.4 Runtime Update:

  • Max buffer size fix for file system full [SE-11147]

March 15, 2019

3.9.1 Runtime Update:

  • Schedules not registered [SE-11264]

March 8, 2019

3.8.7 Runtime Update:

  • Dnsmasq unavailable [SE-11197]

3.8.6 Runtime Update:

  • Dnsmasq unavailable [SE-11197]

3.8.5 Runtime Update:

  • Dnsmasq unavailable [SE-11197]

March 7, 2019

4.1.5 Runtime Update:

  • Batch fails in CloudHub with persistent queues enabled [SE-10583]

4.1.4 Runtime Update:

  • Batch fails in CloudHub with persistent queues enabled [SE-10583]

March 6, 2019

4.1.5 Runtime Update:

  • Incorrect handling of backslashes in logger component [SE-10940]

  • NullPointerException when MUnit tries to dispose of object after test [SE-10038]

4.1.4 Runtime Update:

  • NullPointerException when MUnit tries to dispose of object after test [SE-10038]

3.9.2 Runtime Update:

  • Partitioned object store does not delete partition folder [SE-10999]

  • Hung thread in WMQ transport with synchronous processing strategy [SE-10743]

3.9.1 Runtime Update:

  • Hung thread in WMQ transport with synchronous processing strategy [SE-10743]

3.8.7 Runtime Update:

  • Partitioned object store does not delete partition folder [SE-10999]

  • Memory leak in XsltTransformer [SE-8522]

3.8.6 Runtime Update:

  • Partitioned object store does not delete partition folder [SE-10999]

  • Memory leak in XsltTransformer [SE-8522]

3.8.5 Runtime Update:

  • Cache not being cleaned in throttling policy [SE-10534]

February 27, 2019

4.1.5 Runtime Update:

  • Context does not contain key error shown in the logs [SE-10867]

4.1.4 Runtime Update:

  • Context does not contain key error shown in the logs [SE-10867]

February 26, 2019

3.9.2 Runtime Update:

  • Detect Mule unresponsiveness through ping flow

3.9.1 Runtime Update:

  • Detect Mule unresponsiveness through ping flow

3.9.0 Runtime Update:

  • Detect Mule unresponsiveness through ping flow

February 15, 2019

3.9.1 Runtime Update:

  • Include Anypoint Monitoring Agent Extension

3.9.0 Runtime Update:

  • Include Anypoint Monitoring Agent Extension

February 14, 2019

4.1.5 Runtime Update:

  • Address incomplete fix of performance degradation caused by high volume of logging [SE-10742]

February 7, 2019

4.1.5 Runtime Update:

  • ThreadLocal configuration causes performance degradation [SE-10742]

  • Salesforce Marketing connector throws token expired exception [SE-10343]

4.1.4 Runtime Update:

  • Salesforce Marketing connector throws token expired exception [SE-10343]

February 2, 2019

4.1.5 Runtime Update:

  • Gatekeeper policy causes memory leak on policy engine [SE-10641]

4.1.4 Runtime Update:

  • Gatekeeper policy causes memory leak on policy engine [SE-10641]

February 1, 2019

3.9.2 Runtime Update:

  • Include Anypoint Monitoring Agent Extension

January 25, 2019

3.9.2 Runtime Update:

  • ObjectDoesNotExistException on OAuth module [SE-10423]

  • XSD schemas being loaded multiple times cause delayed startup [SE-10529]

3.9.1 Runtime Update:

  • ObjectDoesNotExistException on OAuth module [SE-10423]

  • XSD schemas being loaded multiple times cause delayed startup [SE-10529]

January 24, 2019

4.1.5 Runtime Update:

  • DataWeave distinct operation runs out of memory with a large collection [SE-10548]

  • High CPU usage on DataWeave transformation causes the worker to stop processing [SE-10638]

4.1.4 Runtime Update:

  • DataWeave distinct operation runs out of memory with a large collection [SE-10548]

  • High CPU usage on DataWeave transformation causes the worker to stop processing [SE-10638]

January 2, 2019

4.1.5 Runtime Update:

  • Source error callback is not called when an error is caught in error handler [SE-10212]

4.1.4 Runtime Update:

  • Source error callback is not called when an error is caught in error handler [SE-10212]

3.9.2 Runtime Update:

  • WMQ transport with synchronous processing strategy is not reconnecting [SE-10362]

3.9.1 Runtime Update:

  • WMQ transport with synchronous processing strategy is not reconnecting [SE-10362]

3.9.0 Runtime Update:

  • WMQ transport with synchronous processing strategy is not reconnecting [SE-10362]

December 18, 2018

4.1.5 Runtime Update:

  • ProcessingStrategy internal bufferSize is always 256 for flow-ref [SE-10226]

  • IdempotentRedeliveryPolicy blocks CPU_LITE thread [SE-10306]

4.1.4 Runtime Update:

  • ProcessingStrategy internal bufferSize is always 256 for flow-ref [SE-10226]

  • IdempotentRedeliveryPolicy blocks CPU_LITE thread [SE-10306]

December 13, 2018

3.9.2 Runtime Update:

  • Diagnostic logs download [SE-10249]

3.9.1 Runtime Update:

  • Diagnostic logs download [SE-10249]

3.9.0 Runtime Update:

  • Diagnostic logs download [SE-10249]

December 12, 2018

4.1.4 Runtime Update:

  • Diagnostic logs download [SE-10249]

4.1.3 Runtime Update:

  • Diagnostic logs download [SE-10249]

4.1.2 Runtime Update:

  • Diagnostic logs download [SE-10249]

4.1.1 Runtime Update:

  • Diagnostic logs download [SE-10249]

4.1.0 Runtime Update:

  • Diagnostic logs download [SE-10249]

December 10, 2018

3.9.2 Runtime Update:

  • MEL expression failure with concurrent requests [SE-10166]

3.9.1 Runtime Update:

  • MEL expression failure with concurrent requests [SE-10166]

  • OAuth provider does not honor expired token TTL [SE-8650]

  • LIST command is not issued after reconnection in FTP transport [SE-9323]

  • APIKit validation error doesn’t display the field name [SE-8727]

3.9.0 Runtime Update:

  • OAuth provider does not honor expired token TTL [SE-8650]

  • LIST command is not issued after reconnection in FTP transport [SE-9323]

December 7, 2018

4.1.4 Runtime Update:

  • Invalid XML generated for artifact declaration [MULE-15835]

4.1.3 Runtime Update:

  • Invalid XML generated for artifact declaration [MULE-15835]

December 6, 2018

3.9.2 Runtime Update:

  • Wrapper working directory [SE-10173]

  • Security enhancements

3.9.1 Runtime Update:

  • Wrapper working directory [SE-10173]

  • Security enhancements

3.9.0 Runtime Update:

  • Wrapper working directory [SE-10173]

  • Security enhancements

December 5, 2018

4.1.4 Runtime Update:

  • Batch persistent queue initialization [SE-9688]

  • Wrapper working directory [SE-10173]

  • Expose mule deployment error [SE-8554, SE-9209]

  • Security enhancements

4.1.3 Runtime Update:

  • Batch persistent queue initialization [SE-9688]

  • Wrapper working directory [SE-10173]

  • Expose mule deployment error [SE-8554, SE-9209]

  • Security enhancements

4.1.2 Runtime Update:

  • Batch persistent queue initialization [SE-9688]

  • Wrapper working directory [SE-10173]

  • Security enhancements

4.1.1 Runtime Update:

  • Batch persistent queue initialization [SE-9688]

  • Wrapper working directory [SE-10173]

  • Security enhancements

4.1.0 Runtime Update:

  • Batch persistent queue initialization [SE-9688]

  • Wrapper working directory [SE-10173]

  • Security enhancements

November 26, 2018

4.1.4 Runtime Update:

  • Amazon SQS connector shutdown exception. [SE-9149]

  • Backpressure is not triggered by a saturated CPU_INTENSIVE thread pool. [SE-10078]

4.1.3 Runtime Update:

  • Amazon SQS connector shutdown exception. [SE-9149]

November 22, 2018

4.1.4 Runtime Update:

  • 'Could not deserialize object' in cache component. [SE-9879]

  • DataWeave stream closed intermittently in a batch process. [SE-9974]

  • DataWeave flatten() function is not streaming. [SE-10077]

November 10, 2018

4.1.4 Runtime Update:

  • Invalid Session ID on SFDC connector reconnnection attempt. [SE-9471]

4.1.3 Runtime Update:

  • Invalid Session ID on SFDC connector reconnnection attempt. [SE-9471]

November 9, 2018

4.1.4 Runtime Update:

  • DataWeave stream is closed before being consumed in batch aggregator [SE-9836]

  • Batch process not doing "on complete" step when results collection is empty [SE-9899]

3.9.1 Runtime Update:

  • Addressed deployment issue when using the IMAP reconnection strategy. [SE-9544]

3.9.0 Runtime Update:

  • Response encoding is replaced in Web Service Consumer. [SE-9298]

November 5, 2018

3.9.0 Runtime Update:

  • Let customer fix invalid cron schedules after start [SE-8632]

  • Internal HTTP client enhancements

  • Security enhancements

3.9.1 Runtime Update:

  • Let customer fix invalid cron schedules after start [SE-8632]

  • Internal HTTP client enhancements

  • Security enhancements

November 2, 2018

4.0.0 Runtime Update:

  • License update [SE-9564]

  • Expose mule deployment error [SE-8554, SE-9209]

  • Security enhancements

4.1.0 Runtime Update:

  • License update [SE-9564]

  • Expose mule deployment error [SE-8554, SE-9209]

  • Security enhancements

4.1.1 Runtime Update:

  • License update [SE-9564]

  • Expose mule deployment error [SE-8554, SE-9209]

  • Security enhancements

4.1.2 Runtime Update:

  • License update [SE-9564]

  • Expose mule deployment error [SE-8554, SE-9209]

  • Security enhancements

October 30, 2018

3.8.5 Runtime Update:

  • Payload expression transform error [SE-9452]

October 29, 2018

4.1.4 Runtime Update:

  • Cron schedulers were not properly registered [SE-9861]

October 26, 2018

4.1.4 Runtime Update:

  • Event instances were kept too long in the buffer [SE-9556]

  • Expose mule deployment error [SE-8554, SE-9209]

3.9.1 Runtime Update:

  • NullPointerException while refreshing access token in OAuth with Client Credentials [SE-9613]

  • Response encoding being replaced in Web Service Consumer [SE-9298]

  • Payload expression transform error [SE-9452]

  • Expose mule deployment error [SE-8554, SE-9209]

3.9.0 Runtime Update:

  • Attachment order not being honored in multipart-form-data request [SE-7595]

  • Expose mule deployment error [SE-8554, SE-9209]

3.8.5 Runtime Update:

  • Attachment order not being honored in multipart-form-data request [SE-7595]

  • Transformation graph incorrectly overridden [SE-7162]

October 9, 2018

4.1.3 Runtime Update:

  • Object Store V2 plugin update fixing the encoding of keys when deleting causing not found issue [SE-9505]

  • Batch crashes with ArrayList of HashMap as input [SE-9437]

  • SDK scopes process internal chains as blocking [SE-9315]

  • Cannot open a new cursor on a closed stream using batch processing [SE-9472]

  • DataWeave buffer output FileNotFoundException [SE-9379]

  • Failure to process subflow with async scopes [SE-9395]

October 5, 2018

3.9.1 Runtime update:

  • Updated Object Store v2 plugin version to fix exception not being thrown as the Mule ObjectStore contract specifies. [SE-9551]

3.9.0 Runtime update:

  • Updated Object Store v2 plugin version to fix exception not being thrown as the Mule ObjectStore contract specifies. [SE-9551]

3.8.7 Runtime update:

  • Updated Object Store v2 plugin version to fix exception not being thrown as the Mule ObjectStore contract specifies. [SE-9551]

3.8.6 Runtime update:

  • Updated Object Store v2 plugin version to fix exception not being thrown as the Mule ObjectStore contract specifies. [SE-9551]

3.8.5 Runtime update:

  • Updated Object Store v2 plugin version to fix exception not being thrown as Mule the ObjectStore contract specifies ,[SE-9551]

September 21, 2018

4.1.2 Runtime update:

  • Client Enforcement Policy throwing "No value present" error [SE-8736]

4.1.1 Runtime update:

  • Change token expiration log level from ERROR to WARN [SE-8613]

  • Client Enforcement Policy throwing "No value present" error [SE-8736]

3.9.1 Runtime update:

  • OAuth2 provider not working when offline; support RestClient reconnection [SE-9455]

  • RAML parser uncaught exception [SE-9228]

  • API console RAML validatioan errors [SE-8773]

September 17, 2018

4.1.3 Runtime Update:

  • DW2 lookup function blocks CPU intensive threads [SE-9104]

  • Ability to send "Base64 Encoded client_id and client_secret" in Authorization header for authorization-code-grant-type [SE-9065]

  • Unknown error on Object Store operation [SE-9285]

3.9.1, 4.1.2, 4.1.3 Runtime Updates:

  • Error related to Application Visualizer seen in multiple applications in CloudHub [SE-9143]

August 23, 2018

All 3.8.x, 3.9.x and 4.1.x Runtime Updates:

  • A kernel-level patch to the operating system against the SegmentSmack vulnerability (CVE-2018-5390)

August 14, 2018

4.1.3 Runtime Update:

  • Cache locks CPU lite threads under load. Addressed incomplete fix. [SE-8937]

4.1.2 Runtime Update:

  • Cache locks CPU lite threads under load. Addressed incomplete fix. [SE-8937]

  • SFTP connector not closing connections [SE-8996]

4.1.1 Runtime Update:

  • Cache locks CPU lite threads under load. Addressed incomplete fix. [SE-8937]

  • SFTP connector not closing connections [SE-8996]

July 31, 2018

3.8.7 Runtime Update:

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

3.8.6 Runtime Update:

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

3.8.5 Runtime Update:

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

3.9.1 Runtime Update:

  • StackOverflow on Exception in non-blocking flow [SE-7797]

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

  • Fix Anypoint Visualizer enablement for cached instances

3.9.0 Runtime Update:

  • Infinite loop in non-blocking flow using Scatter Gather [SE-8351]

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

July 30, 2018

4.1.2 Runtime Update:

  • Cache locks CPU lite threads under load [SE-8937]

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

  • Fix Anypoint Visualizer enablement for cached instances

4.1.1 Runtime Update:

  • Cache locks CPU lite threads under load [SE-8937]

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

July 23, 2018

4.1.2 Runtime Update:

  • MuleModuleLoader keeps reference to a BindingContext [SE-8526]

July 18, 2018

4.1.2 Runtime Update:

  • StackOverflow error is non-descriptive [SE-8686]

  • Web Service Consumer ignores CDATA tag in Consume operation [SE-8643]

July 12, 2018

4.1.2 Runtime Update:

  • Implemented retry strategy for Object Store v2 REST client to improve resiliency.

4.1.1 Runtime Update:

  • Implemented retry strategy for Object Store v2 REST client to improve resiliency.

4.1.0 Runtime Update:

  • Implemented retry strategy for Object Store v2 REST client to improve resiliency.

3.9.1 Runtime Update:

  • Implemented retry strategy for Object Store v2 REST client to improve resiliency.

3.9.0 Runtime Update:

  • Implemented retry strategy for Object Store v2 REST client to improve resiliency.

3.8.7 Runtime Update:

  • Implemented retry strategy for Object Store v2 REST client to improve resiliency.

3.8.6 Runtime Update:

  • Implemented retry strategy for Object Store v2 REST client to improve resiliency.

3.8.5 Runtime Update:

  • Implemented retry strategy for Object Store v2 REST client to improve resiliency.

July 10, 2018

4.1.0 Runtime Update:

  • LogAppender instances not cleaned up on redeploy [MULE-15169]

4.1.1 Runtime Update:

  • LogAppender instances not cleaned up on redeploy [MULE-15169]

  • Flow designer deployment fails with HTTP request default header configuration [SE-8088]

  • Batch schema validation failure triggers Serialization Exception [SE-8687]

4.1.2 Runtime Update:

  • LogAppender instances not cleaned up on redeploy [MULE-15169]

  • Flow designer deployment fails with HTTP request default header configuration [SE-8088]

  • Batch schema validation failure triggers Serialization Exception [SE-8687]

  • Mule runtimes versions 3.9.1 and 4.1.2 support Anypoint Visualizer.

  • The 3.9.1-visualizer and 4.1.2-visualizer versions of Mule runtime are deprecated. Use the 3.9.1 and 4.1.2 versions instead.

July 3, 2018

3.8.7 Runtime Update:

  • Fixes NullPointerException in Grizzly ClientHttpResponseImpl.getProcessingState() [SE-8085]

4.1.2 Runtime Update:

  • Fixes DataWeave flatfile transformation returns empty payload [SE-8608]

  • Fixes DefaultEventContext not cleaned up [SE-8526]

June 30, 2018

  • Mule runtime version 3.9.1-visualizer and 4.1.2-visualizer for CloudHub have been released. These runtimes must be used for the application and its dependencies to viewed in Anypoint Visualizer.

June 29, 2018

All 3.8.x, 3.9.x and 4.1.x Runtimes:

  • Adds 256mb SWAP drive for 0.1vCores to address rare scenarios of Native OS out of memory [SE-7207]

  • Fixes an issue where extra properties are injected when monitoring process restarts mule [SE-8590]

All 4.1.x Runtimes:

  • NPE on application startup with specific configuration [MULE-15141]

  • Fixes deployment of an specific application using a system property [MULE-15167]

  • Upgrade Agent to 2.1.3

3.8.4 Runtime Update:

  • Fixes leak on the CXF component (org.apache.cxf.endpoint.ClientImpl) [SE-6455,SE-8107]

3.9.0 Runtime Update:

  • BufferUnderflowException in DataWeave tranformation [SE-7263]

3.9.1 Runtime Update:

  • Fixes leak on the CXF component (org.apache.cxf.endpoint.ClientImpl) [SE-8107]

June 18, 2018

3.9.0 Runtime Update comes with the following fixes:

  • Backoff scheduler log line is always present [SE-8290]

3.9.1 Runtime Update comes with the following fixes:

  • Backoff scheduler log line is always present [SE-8290]

June 6, 2018

3.9.0 Runtime Update comes with the following fixes:

  • Address partial fix for SE-7615 [SE-8370]

  • Metadata replay empties the payload [SE-7081]

  • DW buffer files not being deleted when calling dw() from MEL on large payloads [SE-8423]

3.9.1 Runtime Update comes with the following fixes:

  • Performance degradation with empty MessageProcessorNotificationListener [MULE-14901]

  • DW buffer files not being deleted when calling dw() from MEL on large payloads [SE-8423]

4.1.2 Runtime Update comes with the following fixes:

  • Performance degradation with empty MessageProcessorNotificationListener [MULE-14901]

  • Unable to invoke a service using a WSDL with nested imports [SE-8362]

May 21, 2018

3.9.1 Runtime Update comes with the following fixes:

  • Flow-ref response time increasing over time [SE-8100]

3.9.0 Runtime Update comes with the following fixes:

  • Flow-ref response time increasing over time [SE-8100]

3.8.6 Runtime Update comes with the following fixes:

  • Flow-ref response time increasing over time [SE-8100]

May 11, 2018

3.9.0 Runtime Update comes with the following enhancement:

  • Data Weave does not consider DST +-1H change when converting UTC time stamp to local time stamp [SE-8039]

  • AbstractDbMessageProcessor is leaking connections [SE-7982]

  • BufferUnderflowException on Dataweave transformations [SE-7263]

  • SFTP Password is not masked when special character(^) is used

May 7, 2018

3.8.6 Runtime Update comes with the following enhancement:

  • Data Weave does not consider DST +-1H change when converting UTC time stamp to local time stamp [SE-8039]

  • AbstractDbMessageProcessor is leaking connections [SE-7982]

  • BufferUnderflowException on Dataweave transformations [SE-7263]

April 5, 2018

3.9.0 Runtime Update comes with the following enhancement:

  • Updated the Object Store V2 plugin to provide better error messages

April 4, 2018

3.8.3 Runtime Update comes with the following fixes:

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

  • Mime Type Dissapears when under load [SE-7807]

3.8.4 Runtime Update comes with the following fixes:

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

March 30, 2018

3.8.5 Runtime Update comes with the following fixes:

  • Automatic retry on remote Closed exception does not respect RFC 7320 [SE-7116]

  • SFTP Reconnect throws "Already in lifecycle phase" as a error message [SE-6658]

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

  • Warning logs are emitted when using secured properties [SE-7445]

March 29, 2018

3.8.6 Runtime Update comes with the following fixes:

  • Mime Type Dissapears when under load [SE-7807]

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

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

March 28, 2018

3.9.0 Runtime Update comes with the following fixes:

  • Dynamic flow reference from a For-Each causes 'ConcurrentModificationException' [SE-7060]

  • SAXParseException when customer is using schema validation in CXF and schema has dependency on other schemas [SE-6358]

  • Mime Type Dissapears when under load [SE-7807]

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

  • DataWeave transformation throws BufferUnderflowException [SE-7263]

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

  • Warning logs are emitted when using secured properties [SE-7445]

March 26, 2018

3.8.6 Runtime Update comes with the following fix:

  • Warning logs are emitted when using secured properties [SE-7445]

March 22, 2018

3.9.0 Runtime Update comes with the following fixes:

  • Fixes an issue where logs are filled up with "skip invalid notification" message when insight is enabled [SE-7552]

  • Fixes an issue where dates weren’t being validate [SE-7622]

  • Fixes NPE thrown by the raml java parser [RP-253]

March 21, 2018

3.8.6, 3.8.5, 3.8.4, and 3.8.1 Runtime Updates come with the following enhancement:

  • Adds more properties in batch notifications when using Insights

February 26, 2018

3.9.0 and 3.8.6 Runtime Updates comes with the following fixes:

  • Fixes an issue where Rate-limiting SLA Based policy applied inconsistently [SE-7099]

  • Fixes a deadlock caused by Grizzly library [SE-7388]

  • Fixes an issue with Concurrent Refresh token requests [SE-7615]

3.9.0 Runtime Update comes with the following fixes:

  • Fixes an issue where STFP Reconnect throws incorrect error [SE-6658]

  • Fixes an issue where Automatic retry on remote Closed exception does not respect RFC 7320 [SE-7116]

February 1, 2018

3.9.0 and 3.8.5 Runtime Update comes with the following improvement:

  • Fixes a performance overhead added by APIKit Router [APIKIT-1146]

January 24, 2018

3.8.6 Runtime Update comes with the following improvements:

  • Fixes a performance overhead added by APIKit Router [APIKIT-1146]

  • Fix unwanted Java warning messages when using secure properties

January 15, 2018

3.8.3 Runtime Update comes with the following fix:

  • kernel-level patch to the operating system to protect against the Speculative Execution vulnerability (CVE-2017-5754)

3.9.0 Runtime Update comes with the following improvements:

  • Fixes an issue where the RAML java parser fails parsing a DataType that import a library [SE-7329]

  • Fixes an incorrect processing of query parameters by APIKit [SE-7407]

January 5, 2018

The following runtime updates includes a kernel-level patch to the operating system to protect against the Speculative Execution vulnerability (CVE-2017-5754).

  • 4.0.0

  • 3.9.0

  • 3.8.6

  • 3.8.5

  • 3.8.4

  • 3.7.5

  • 3.5.4

  • 2.2.1-API-Gateway

December 20, 2017

3.8.6 Runtime Update comes with the following fix:

  • Updated the version of Object Store plugin to respect the request timeout configuration value from Mule

December 12, 2017

3.9.0 Runtime Update comes with the following fix:

  • Fixes an issue that API Gateway shows unwanted log line [SE-7087]

3.8.5 Runtime Update comes with the following improvement:

  • Set HeapMemoryManager as Default Grizzly Memory Manager [MULE-12745]

  • Fixes an issue where APIKit incorrectly overrides the default transformation graph [APIKIT-1092]

November 14, 2017

3.9.0 and 3.8.5 Runtime Update comes with the following fix:

  • Fixes the failure that occurs when attempting to access an XSD file with WSDL with an HTTP/HTTPS base path [MULE-13934]

3.8.5 and 3.8.4 Runtime Update comes with the following fix:

  • Fixes an issue where ObjectToJMSMessage does not register source types [MULE-13974]

3.8.5 Runtime Update comes with the following fix:

  • Fixes an issue where SFTP logging does not mask credentials with special regex chars in password [MULE-13978]

3.8.4 Runtime Update comes with the following fix:

  • Fixes an issue where APIKit incorrectly overrides the default transformation graph [APIKIT-1092]

November 6, 2017

3.9.0, 3.8.5, and 3.8.4 Runtime updates come with the following fix:

  • Fixes an issue where PollingReceiverWorker did not clean RequestContext after performing a poll [MULE-13698]

3.8.5 and 3.8.4 Runtime updates come with the following fixes:

  • Fixes an issue where setting inboundValidationMessage to true in SOAP kit resulted in the error cannot be cast to org.codehaus.stax2.XMLStreamReader2 [MULE-13167]

  • Fixes a problem where CXF Proxy throws NPE when schemas are imported in a WSDL [MULE-7794]

3.8.5 Runtime update comes with the following fix:

  • Fixes an issue where SFTP DSA verification is rejected as an invalid verification code using JDK 1.8.0_121 onwards [MULE-13465]

October 24, 2017

3.8.3 Runtime Update comes with the following fixes:

  • Fix the issue where Replay does not work with DataWeave, VM, Transformers and HTTPS requests [SE-6653,4475,6508,6681]

  • Fixes an issue where calls to multiple DNS servers were being made simultaneously

October 18, 2017

3.8.2 Runtime Update comes with the following fix:

  • Fix the issue where Replay does not work with DataWeave, VM, Transformers and HTTPS requests [SE-6653,4475,6508,6681]

October 17, 2017

3.9.0 is now available in Cloudhub

October 5, 2017

3.8.5 Runtime Updates comes with following fix:

  • Propagation of SSL prevents Jackson serialization of InboundProperties

  • CORS policy is missing Access-Control-Expose-Header support for simple requests

  • Avoid unnecessary wrapping of inbound endpoints with GatewayMessageSource

  • XSD’s imported in WSDL referenced as bare file results in warning while creating request body

  • Fix the issue where Replay does not work with DataWeave, VM, Transformers and HTTPS requests [SE-6653,4475,6508,6681]

October 2, 2017

3.8.3 Runtime Updates comes with following fix:

  • Propagation of SSL prevents Jackson serialization of InboundProperties

September 17, 2017

3.8.3 Runtime Updates comes with following fix:

  • OAuth Module with TLS causing Leak [SE-6762]

September 15, 2017

3.8.1, 3.8.2, 3.8.3, 3.8.4, 3.8.5 Runtime Updates come with following fix:

  • Fix to avoid an incorrect processing of query parameters by the RAML java parser [SE-6751]

September 13, 2017

3.8.3, 3.8.5 Runtime Updates come with the following fix:

  • Fixes an issue where Cloudhub Mule Monitor dies and prevent restart [SE-6649]

3.8.3 Runtime Update comes with the following fixes:

  • Fixes an issue where Event Tracking blocks Message Source thread [SE-6147]

  • Fixes a problem where Worker Unresponsive alert is triggered on a healthy worker [SE-6365]

September 8, 2017

3.7.5 Runtime Update comes with the following improvements:

  • Fixes an issue where Event Tracking blocks Message Source thread [SE-6147]

  • Fixes a problem where Worker Unresponsive alert is triggered on a healthy worker [SE-6365]

August 29, 2017

3.8.5 Runtime Update comes with the following improvements:

  • Fixes an issue where Event Tracking blocks Message Source thread [SE-6147]

  • Fixes a problem where Worker Unresponsive alert is triggered on a healthy worker [SE-6365]

August 4, 2017

3.8.5 Runtime Update comes with the following improvements:

  • Better logging for Replay Transactions

  • Increased retries for storing replay data

  • Added request timeout for storing replay data

  • Increased maximum payload size for replay transactions

3.7.0, 3.7.1, 3.7.2, 3.7.3, 3.7.4, 3.7.5 Runtime Updates come with the following improvement:

  • Support for Persistent Queues in new regions

August 1, 2017

3.8.0, 3.8.1, 3.8.2, 3.8.4 Runtime Updates come with following fix:

  • Fixes an issue with Persistent Queues raising java.lang.NoSuchMethodError [SE-6421]

July 27, 2017

3.8.3 and 3.8.5 Runtimes Update comes with the following fix:

  • Fixes an issue with Persistent Queues raising java.lang.NoSuchMethodError [SE-6421]

3.8.5 Runtime Update comes with the following fix:

  • Fixes a problem where dw-buffer-input*.tmp file is getting created in tmp directory [SE-6424]

  • Fixes an issue where API Console does not render in Studio [FV-103]

  • Fixes an issue where Includes with absolute paths are not resolved in Studio [APIKIT-888]

  • Fixes an issue where APIKit examples were not being generated taking into account the response mimetype [APIKIT-752]

July 19, 2017

3.8.4 Runtime Update comes with the following fix:

  • Fixes a configuration problem that prevented HTTP Request responseTimeout from being honored when doing non-preemptive authentication HTTP calls and caused the HTTP requester to throw an exception if the remote side sends a close connection header

July 13, 2017

3.8.0, 3.8.1, 3.8.2, 3.8.3 and 3.8.4 Runtime Update comes with the following fix:

  • Updated Amazon SDK to 1.11.153

3.8.4 Runtime Update also comes with the following fixes:

  • Fixes an issue where HTTP Request responseTimeout is not honored when doing non-preemptive authentication HTTP call [MULE-12943]

  • Fixes an issue related CORS policy when different versions of the same API are deployed in one application

  • Fixes a problem where HTTP requester throws exception if the remote side sends a close connection header

  • Added support for WS-Security with CXF [MULE-12995]

  • Fixes performance issues related to RAML 1.0 Parser

June 22, 2017

3.8.4 Runtime Update comes with the following fix:

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

  • Upgrade JDK to 8u131.

May 18, 2017

3.8.4 Runtime Update comes with the following fixes:

  • Fixes an issue where Multiple JDBC Connector in foreach scope component cause null pointer due to NotificationUtils not checking for null parentElement [MULE-12267]

  • Fixes a problem where XsltTransformer should close underlying InputStream when using XMLStreamReader [MULE-12360]

  • Fixes an issue of race condition in batch when the thread dispatcher reads from the persistent queue which leads to delayed processing in a batch process

  • Fixes an issues related to high CPU due to infinite loop in a batch job

  • Fixes a problem where com.mulesoft.weave.model.values.NameValue$MaterializedNameValue cannot be cast to com.mulesoft.weave.model.capabilities.AttributesCapablet

  • Fixes an issue where large payload is getting dropped while performing only set-variable DW transform

May 9, 2017

3.8.3 Runtime Update comes with the following fix:

  • Fixes an issue where MuleWeaveFactory$.createGlobalContext(…​) blocks threads

May 2, 2017

3.8.4 Runtime Update comes with the following fixes:

  • Fixes a problem where token refresh overrides payload when resending request [MULE-11949]

  • Fixes issue where SedaStageInterceptingMessageProcessor thread should clear RequestContext [MULE-12206]

  • Fixes an issue where MuleWeaveFactory$.createGlobalContext(…​) blocks threads

  • Fixes a problem with High CPU usage caused by internal configuration

3.8.3 Runtime Update comes with the following fixes:

  • MVEL optimizer does not refresh when the payload type changes [MULE-11274]

April 12, 2017

3.8.4 runtime update

March 21, 2017

This runtime update comes with the following fixes:

  • Fixes an issue where after until-successful flow variables loses mime type [MULE-11382]

  • Fixes a problem with DataWeave FlatFile transformation not working as expected when unbounded nested segments are in place

  • Fixes an issue with HTTP requester when sending request to Microsoft IIS

  • Fixes a problem where Oauth authentication uses refreshToken when parameter is overriding payload [MULE-11949]

  • Fixes an issue where Mule Listener stopped serving request after one grizzly listener is killed due to NoClassDefFoundError [MULE-11337]

These updates are available for Mule Runtime version 3.8.3

March 2, 2017

Patched API Gateway 2.2.0 with MULE-9163 fix.

February 7, 2017

Patched 3.8.x runtimes to upgrade to Python 3 and accommodate to AWS new instances id (long id).

December 1, 2016

This set of runtime updates includes the following:

  • Fixes a vulnerability with JAXB and Jersey which could result in a DoS attack

  • Fixes a problem where a 403 error would appear in the logs when using Insight

These updates will be released for the following versions: 3.5.0, 3.5.1, 3.5.2, 3.5.3, 3.5.4, 3.6.0, 3.6.1, 3.6.2, 3.6.3, 3.6.4, 3.7.0, 3.7.1, 3.7.2, 3.7.3, 3.7.4, 3.8.0, 3.8.1, 3.8.2, API Gateway 2.0.2, API Gateway 2.0.3, API Gateway 2.0.4, API Gateway 2.1.0, API Gateway 2.1.1, API Gateway 2.2.0

November 23, 2016

This set of runtime updates includes the following:

  • Fixes a vulnerability with JAXB and Jersey which could result in a DoS attack

  • Fixes a problem where a 403 error would appear in the logs when using Insight

  • Fixes an issue with DataWeave which would result in running out of space on the drive for 3.8.x

  • Fixes an issue with APIkit where it would cast a numeric string query param to Integer, which then caused a InvalidQueryParameterException

Runtimes updated include 3.5.4, 3.7.4, and 3.8.2

Was this article helpful?

💙 Thanks for your feedback!