Contact Us 1-800-596-4880
  1. Homepage
  2. Release Notes

  3. Mule Runtime Engine 4.8.0 Release Notes

Mule Runtime Engine 4.8.0 Release Notes

Mule runtime engine (Mule) is a lightweight integration engine that runs Mule applications and supports domains and policies.

This version of Mule provides important enhancements and fixes. Deploy all your new and existing applications to the latest version to benefit from the improvements.

February 2025

Patch 4.8.5

The February patch update 4.8.5 addresses a regression in the previous February patch update, 4.8.4, and includes the fixes in the patch.

Patch release version: 4.8.5

This patch update addresses the following Mule issues:

Description Issue

ConfigurationException no longer occurs while performing Amazon DynamoDB Connector operations.

W-17801971

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

Patch 4.8.4

What’s New

Runtime Manager agent:

Fixed Issues

Patch release version: 4.8.4

This patch update addresses the following Mule issues:

Issue Resolution ID

A ClassCastException thrown when an error occurs within an on-error-continue component no longer prevents transactions from rolling back.

W-17430963

The io.netty:netty-commonis is upgraded to 4.1.115.

W-17431962

InterceptionException is no longer thrown while running MUnit test containing a batch job.

W-17395302

The optimization to avoid sending body contents on NTLM type 1 requests added in W-17107281 is now controlled by the feature flag mule.ntlm.avoid.send.payload.on.type1.

W-17216089

Kryo serialization issue no longer occurs in Java 17 when running with distributed cluster using authentication, caching policy, and persistent Object Store.

W-16912085

The Xerces-J is upgraded to 2.12.2.

W-16980865

An infinite loop no longer occurs for a redelivery policy when the redelivery is exhausted in a source configured with transactions and On Error Propagate.

W-17405939

The installLicense option no longer fails to locate the license file when using a relative path.

W-17379726

API metrics are now properly sent.

W-17529530

Transactions initiated before a flow-ref call are now rolled back in the correct place if an error propagates from the flow-ref.

W-17453707

A corner case has been fixed and Anypoint Monitoring dashboard now correctly shows all metrics.

W-16828516

DataWeave 2.8.3 is bundled with the Mule 4.8.4 release. This patch release addresses the following DataWeave issues:

Issue Resolution ID

The Java reflection lookup strategy is now improved for bean instances.

W-17624594

Compatibility flags created with Mule runtime 4.4 can now be used with older Mule runtime versions.

W-17372664

The deconstruct pattern now works as expected when using append on empty objects combined.

W-16823030

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

January 2025

Patch 4.8.3

  • This patch update reverts the fixes for the following Mule issues: W-17107281 and W-17048606.

  • This patch update reverts the fixes for the following DataWeave issues: W-16823030, W-17206423, and W-17372664.

Patch 4.8.2

What’s New

Runtime Manager agent:

Fixed Issues

Patch release version: 4.8.2

This patch update addresses the following Mule issues:

Issue Resolution ID

Windows no longer throws cannot delete file errors during application undeploy.

W-17050930

BufferOverFlowException with inter-node communication getting stuck no longer occurs when using clusters with encryption under heavy load.

W-16517561

Unnecessary internal blocking operations no longer occur when handling large streamed HTTP responses.

W-17048606

Body content is no longer sent on Type 1 requests during NTLM authentication.

W-17107281

Deploying applications that contain XML SDK connectors no longer causes application class loader memory leak.

W-16814280

ConnectionException no longer occurs when using batch processing.

W-17008722

A memory leak no longer occurs when using mule-validation-module.

W-16789548

MessageProcessorNotificationListener is no longer called multiple times when running MUnit suites.

W-11866494

A serialization error no longer occurs in Java 17 when using clustering mode or Object Store v2.

W-17218707

IllegalAccessException is no longer thrown during cache scope serialization with Kryo.

W-17089503

All transactions running within a global Error Handler are now committed as expected.

W-16619771

NullPointerException no longer occurs when undeploying an application with native libraries in Windows OS.

W-16712841

com.hazelcast:hazelcast dependency is upgraded to 5.3.8.

W-16594688

NullPointerException is no longer thrown on HTTP requests that use config-ref with dynamic configuration.

W-16602622

DataWeave 2.8.2 is bundled with the Mule 4.8.2 release. This patch release addresses the following DataWeave issues:

Issue Resolution ID

The deconstruct pattern now works as expected when using append on empty objects combined.

W-16823030

The Java reflection lookup strategy is now improved for bean instances.

W-17206423

Compatibility flags created with Mule runtime 4.4 can now be used with older Mule runtime versions.

W-17372664

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

November 2024

What’s New

Runtime Manager agent:

Fixed Issues

Patch release version: 4.8.1

This patch update addresses the following Mule issues:

Issue Resolution ID

Memory leak in MuleApplicationClassloader no longer occurs while undeploying an application.

W-16823349

A batch serialization error no longer occurs in Java 17 when one of the steps throws SQLException.

W-16546951

A deadlock no longer occurs when consuming the payload in the completion callback of the HTTP client sendAsync method.

W-16640190

Web Service Consumer Connector and RosettaNet Connector no longer fail when there’s an HTTP TLS transport configuration.

W-16288302

Log4j2 monorepo is upgraded to 2.24.1.

W-16889265

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

W-15643200

NullPointerException no longer occurs when undeploying an application with native libraries in Windows OS.

W-16712841

Kryo serialization issues no longer occur for rate limit policies using Java 17.

W-16843706

DataWeave 2.8.1 is bundled with the Mule 4.8.1 release. This patch release addresses the following DataWeave issues:

Issue Resolution ID

The stripTrailingZeroes compatibility flag is now added to preserve the decimal format.

W-17030593

Apache POI folder used for temporal files is no longer deleted.

W-16899674

Using annotations without importing them now returns the corresponding error.

W-16853915

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

October 8, 2024

What’s New

The 4.8.0 version of Mule runtime introduces the following enhancements:

Release cadence support coverage:

  • The LTS channel now offers 18 months of Standard Support and 6 months of Extended Support, with a six-month overlap between minor LTS versions, starting with Mule 4.6 LTS. The Edge channel now provides 5 months of Standard Support and 3 months of Extended Support, ensuring a one-month overlap between minor Edge versions, starting with Mule 4.8 Edge.
    See Edge and LTS Releases for Mule.

Feature Flagging Mechanism:

  • Mule 4.8 incorporates new feature flags. See Feature Flagging for a detailed description of each feature flag and configuration instructions.

Runtime Manager agent:

General improvements:

  • The org.apache.maven.plugins:maven-compiler-plugin dependency is upgraded to 3.13.0.

  • The commons-io:commons-io is upgraded to 2.16.1.

  • The dependency org.jruby:jruby-complete is upgraded to 9.4.7.0.

  • The io.opentelemetry:opentelemetry-bom is upgraded to 1.37.0.

  • The org.springframework.security:spring-security-core is upgraded to 5.7.12.

  • The dependency com.google.code.gson:gson is upgraded to 2.11.0.

DataWeave Features

The 2.8.0 version of DataWeave introduces the following new features and enhancements:

Reuse types:

General improvements:

Fixed Issues

The release addresses the following Mule issues and incorporates all patch updates from the 4.7.0 Mule release through September 2024:

Issue Resolution ID

The io.opentelemetry:opentelemetry-bom is upgraded to 1.37.0.

W-15478554

The org.springframework.security:spring-security-core is upgraded to 5.7.12.

W-15761385

The dependency com.google.code.gson:gson is upgraded to 2.11.0.

W-15838633

A validation is added to ensure that domains using the import target have the same top-level element as the importing file.

W-15509819

InitialisationException is no longer thrown when using the Raise Error component with an extra space at the end of the type field.

W-16237424

The configuration-properties encoding parameter is no longer ignored.

W-12228892

ChainInputResolver annotations are no longer ignored if there are no input, output, or metadata key resolvers.

W-16408471

Properties are now resolved during application packaging.

W-15959903

java.lang.InstantiationError : java.util.Map is no longer thrown when applying an authentication policy.

W-16595277

Fatal errors no longer occur when loading native libraries in Java 17.

W-16787783

When the feature flag anypoint.platform.keep.default.policy.format is set to true or the policy min Mule version is at least 4.5.0, the policy name format is ${policyName} @ ${artifactName} - ${flowName}.

W-16169887

The logging for the analytics .db files cleanup is now improved.

W-16624763

Mule Gateway applies Gatekeeper between editions of policy configuration.

W-16225792

DataWeave 2.8.0 is bundled with the Mule 4.8.0 release. This release addresses the following DataWeave issues:

Issue Resolution ID

Configuring a writer as deferred now requires Mule runtime privileges.

W-15398837

The avroschema! module loader is created to enable metadata extraction from Avro schemas.

W-15518930

Type error messages generated in Lambda functions are now improved.

W-16082839

Type inference is now improved when accessing properties of objects.

W-14222927

Type inference inside if/then branches is now improved.

W-15607520

The Avro type now maps to Java’s ArrayBuffer instead of BigDecimal.

W-15607759

The regression is now resolved allowing references to types defined later in the script.

W-15197016

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

W-16125755

Input/output MimeType properties are now preserved as expected.

W-16161736

Access error for Java 17 encapsulation errors is now improved.

W-15705596

Coercion error is now caught inside try as expected.

W-15323897

Bundled Components

  • DataWeave version 2.8.0

  • Runtime Manager Agent plugin version 2.6.5

Upgrade

If you are upgrading to this version of Mule from an earlier Mule 4.x version, see Mule Upgrades and Patch Updates.

To ensure optimal performance with this version of Mule and avoid unexpected issues, update the following modules and extensions to their latest version at the time of this release:

Module or Extension Version

APIkit for Mule 4

1.11.1

APIkit for OData

2.3.0

APIkit for OData 4

1.5.2

APIkit for SOAP

1.5.1

APIkit for GraphQL

1.1.0

Spring module

1.4.0

MUnit plugin

3.3.1

Considerations for Mule Extension Developers

If you update the version of your parent pom.xml file to 1.4.0 or later when you build a Mule extension, ensure that the dependencies in your pom.xml file do not override dependencies defined in the parent pom.xml file, and declare only the dependencies you need. If you need to declare a dependency that is already declared in the parent pom.xml file, do not specify a version so it uses the version from the parent pom.xml file.

See Also