Runtime Manager Agent 2.4.x Release Notes
2.4.37
Jan 12 2023
Fixed Issues
| Issue Resolution | ID |
|---|---|
Runtime Manager Agent Notifications (via REST) now works as expected |
W-11722041 |
Addressed multiple high-severity vulnerabilities in Runtime Manager Agent 2.4.36 associated with Woodstox 3pp |
W-12176621 |
Addressed multiple high-severity vulnerabilities in Runtime Manager Agent 2.4.36 associated with snakeyaml |
W-12355765 |
Compatibility
| Software | Version |
|---|---|
Mule runtime engine |
This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x. |
Java |
JRE/JDK 1.8.0, JDK 11 |
OS |
MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04 |
Runtime Manager |
v2.12.0+ and later |
2.4.36
Nov 15, 2022
What’s New
-
You can now trace WebSocket messages by configuring the
mule.agent.configuration.trace_wsproperty in yourwrapper.conffile, or adding this property in the UI for your Mule. You need to restart your server for it to take this property.
Fixed Issues
| Issue Resolution | ID |
|---|---|
There is now an option to trace WebSocket messages in Mule Agent |
W-10632188 |
Compatibility
| Software | Version |
|---|---|
Mule runtime engine |
This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x. |
Java |
JRE/JDK 1.8.0, JDK 11 |
OS |
MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04 |
Runtime Manager |
v2.12.0+ and later |
2.4.35
Nov 4, 2022
What’s New
-
Added a default implementation for the application jar signer validator with support for keystores with multiple aliases and expired certificate checks on the application validator service.
Fixed Issues
| Issue | ID |
|---|---|
Runtime manager no longer overrides the |
W-11989119 |
Compatibility
| Software | Version |
|---|---|
Mule runtime engine |
This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x. |
Java |
JRE/JDK 1.8.0, JDK 11 |
OS |
MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04 |
Runtime Manager |
v2.12.0+ and later |
2.4.34
Sep 16, 2022
Fixed Issues
| Issue | ID |
|---|---|
Upgraded the versions of several dependency libraries. |
W-11732881 |
Compatibility
| Software | Version |
|---|---|
Mule runtime engine |
This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x. |
Java |
JRE/JDK 1.8.0, JDK 11 |
OS |
MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04 |
Runtime Manager |
v2.12.0+ and later |
2.4.33
Jul 29, 2022
Fixed Issues
| Issue | ID |
|---|---|
Requesting to renew the certificate in Windows now works correctly. |
W-11130919 |
The agent now supports Java 11 with FIPS. |
W-11268395 |
Compatibility
| Software | Version |
|---|---|
Mule runtime engine |
This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x. |
Java |
JRE/JDK 1.8.0, JDK 11 |
OS |
MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04 |
Runtime Manager |
v2.12.0+ and later |
2.4.32
Jul 21, 2022
Fixed Issues
| Issue | ID |
|---|---|
Upgraded the versions of several dependency libraries. |
W-11471229 |
Compatibility
| Software | Version |
|---|---|
Mule runtime engine |
This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x. |
Java |
JRE/JDK 1.8.0 |
OS |
MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04 |
Runtime Manager |
v2.12.0+ and later |
2.4.31
Jun 27, 2022
Fixed Issues
| Issue | ID |
|---|---|
Upgraded the versions of several dependency libraries. |
W-11267482 |
Compatibility
| Software | Version |
|---|---|
Mule runtime engine |
This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x. |
Java |
JRE/JDK 1.8.0 |
OS |
MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04 |
Runtime Manager |
v2.12.0+ and later |
2.4.30
Jun 9, 2022
Fixed Issues
| Issue | ID |
|---|---|
Upgraded the versions of several dependency libraries. |
W-11267437 |
Compatibility
| Software | Version |
|---|---|
Mule runtime engine |
This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x. |
Java |
JRE/JDK 1.8.0 |
OS |
MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04 |
Runtime Manager |
v2.12.0+ and later |
2.4.29
Jun 1, 2022
Fixed Issues
| Issue | ID |
|---|---|
Schedulers no longer start automatically after an application restart, and they retain the same configuration they had before the application stopped. |
W-11032600 |
Changing scheduler configurations no longer causes Fixed Frequency schedulers to restart. |
W-11032600 |
Compatibility
| Software | Version |
|---|---|
Mule runtime engine |
This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x. |
Java |
JRE/JDK 1.8.0 |
OS |
MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04 |
Runtime Manager |
v2.12.0+ and later |
2.4.28
Apr 29, 2022
What’s New
-
Added a new optional validation step to the deployment process. This enables you to write your own application validators to stop a deployment if the given conditions are not satisfied. See feature documentation for details.
| Issue | ID |
|---|---|
Upgraded third-party libraries. |
SE-24290 |
Compatibility
| Software | Version |
|---|---|
Mule runtime engine |
This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x. |
Java |
JRE/JDK 1.8.0 |
OS |
MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, and Ubuntu Server 16.04 |
Runtime Manager |
v2.12.0+ and later |
2.4.27
Feb 03, 2022
What’s New
-
Enabled the Bouncy Castle security provider by adding the property
mule.security.providerwith the value BC to the runtimewrapper.conf, for example,wrapper.java.additional.<n>=-Dmule.security.provider=BC.If you encountered cryptography issues since Mule Agent 2.4.18, you can now use this flag to update the agent version and activate Bouncy Castle as a default security provider.
Compatibility
| Software | Version |
|---|---|
Mule runtime engine |
This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, Mule 4.3.x, and Mule 4.4.x. |
Java |
JRE/JDK 1.8.0 |
OS |
MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04 |
Runtime Manager |
v2.12.0+ and later |
2.4.26
Dec 21, 2021
| Software | Version |
|---|---|
Mule runtime engine |
This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x. |
Java |
JRE/JDK 1.8.0 |
OS |
MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04 |
Runtime Manager |
V2.12.0+ |
2.4.25
Dec 15, 2021
| Software | Version |
|---|---|
Mule runtime engine |
This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x. |
Java |
JRE/JDK 1.8.0 |
OS |
MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04 |
Runtime Manager |
V2.12.0+ |
2.4.24
Dec 14, 2021
Compatibility
| Software | Version |
|---|---|
Mule runtime engine |
This agent version is compatible only with Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x. |
Java |
JRE/JDK 1.8.0 |
OS |
MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04 |
Runtime Manager |
V2.12.0+ |
2.4.23
Nov 10, 2021
| Issue | ID |
|---|---|
Fixed an issue that occurred when deploying an application with scheduler configurations. |
SE-22911 |
| Application/Service | Version |
|---|---|
Mule runtime engine |
Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x. |
Java |
JRE/JDK 1.8.0 |
OS |
MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04 |
Runtime Manager |
V2.12.0+ |
2.4.22
Sep 17, 2021
| Issue | ID |
|---|---|
Upgraded third-party libraries. |
SE-21687 |
| Application/Service | Version |
|---|---|
Mule runtime engine |
Mule 4.1.x, Mule 4.2.x, and Mule 4.3.x. |
Java |
JRE/JDK 1.8.0 |
OS |
MacOS 10.11.x, HP-UX 11i V3, AIX 7.2, Windows 2016 Server, Windows 10, Solaris 11.3, RHEL 7, Ubuntu Server 16.04 |
Runtime Manager |
V2.12.0+ |
2.4.21
2.4.20
June 29, 2021
These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.20.
Fixed Issues
This release includes the following fixes:
-
Custom logging configurations are no longer lost when redeploying an application with a new JAR file.
-
Renew Certificate action via API REST not functioning due to Bouncy Castle dependency conflict.
-
Add validation on configurations while deploying applications on Mule Server. For example, for
mule.agent.application.properties.service, you can only configureapplicationNameandproperties.
2.4.19
June 8, 2021
These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.19.
2.4.18
April 9, 2021
These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.18.
New Features and Enhancements
This release includes the following features:
-
Implemented FIPS compliance for CloudHub.
-
Upgraded the versions of several dependency libraries.
2.4.17
March 12, 2021
These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.17.
New Features and Enhancements
This release includes the following features:
-
Enabled the keystore password encryption in the
mule-agent.ymlfile.
2.4.16
2.4.15
February 12, 2021
These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.15.
New Features and Enhancements
This release includes the following features:
-
Support for FIPS 140-2 on Anypoint Platform PCE.
Fixed Issues
This release includes the following fixes:
-
Fixed a null pointer exception that occurred when sending analytics data to an external database.
-
Fixed an issue that made application deployments unmanaged when restarting domains.
-
Fixed a class cast exception that occurred when redeploying an application after changing the scheduler type.
-
Fixed a file system exception error that occurred while processing the Mule agent configuration file for update.
2.4.14
December 17, 2020
These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.14.
2.4.13
December 11, 2020
These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.13.
2.4.12
December 1, 2020
These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.12.
2.4.11
November 18, 2020
These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.11.
Fixed Issues
This release includes the following fixes:
-
Fixed an issue in which, after restarting the runtime, the properties of the application did not load correctly.
-
Fixed an issue in which deploying an application with secure properties failed on Oracle JDK distributions.
-
Fixed an issue in which the web socket reserved a large amount of memory to buffer connections.
-
Fixed an issue in which analytic data was not sent to external database.
-
Fixed an issue in which sometimes the agent configuration file was corrupted by invalid characters.
2.4.10
October 7, 2020
These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.10.
Fixed Issues
This release includes the following fixes:
-
Fixed an issue in which starting a flow did not start its scheduler.
-
Fixed a null pointer exception that occurred when deploying an application with logging configuration.
-
Fixed a null pointer exception that occurred when deploying an application with missing application properties.
-
Fixed an issue in which starting an application resulted in a
Stoppingstatus in the flows. -
Fixed an issue in which internal agent log messages appeared in the application logs.
-
Fixed an issue in which sometimes the agent configuration file was cleared.
-
Upgraded the versions of several dependency libraries.
2.4.9
2.4.8
2.4.7
July 20, 2020
These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.7.
New Features and Enhancements
The agent now supports the file protocol for application properties.
If an application property is a URI with a file protocol, the agent reads the file content as the property value.
This feature is disabled by default.
To enable it, set the following property in mule-agent.yaml:
services.mule.agent.application.properties.service.fileProtocolConfiguration.enabled: true
For more information, see ARM Mule Agent Plugin API.
Fixed Issues
This release contains the following fixed issues:
-
Fixed an issue in which starting a Mule application after flows become unmanaged caused an error message.
-
Fixed an issue in which restarting a logging service caused an error message.
-
Fixed an issue in which stopping a flow and redeploying the Mule application showed the flow as
stoppinginstead ofstopped. -
The DataWeave preview feature now supports binary content for payload content.
2.4.6
April 7, 2020
These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.6.
Changes in This Release
Reordered the index of the additional Java properties in the wrapper.conf file with the following suffixes:
-
stripquotes -
java_version.min -
java_version.max
2.4.5
January 24, 2020
These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent version 2.4.5.
Changes in This Release
-
Added new modules provided by MuleSoft to the default Runtime Manager agent version 2.x ZIP distribution:
-
Zabbix, Graphite, and CloudWatch metrics publishers
-
DB and HTTP API Analytics trackers
-
2.4.4
December 19, 2019
These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent, version 2.4.4.
Changes in This Release
-
HTTP callbacks now include a new authentication header emitted via the WebSockets channel.
-
Two extra fields were added to the Mule agent REST transport endpoint.
2.4.3
September 26, 2019
These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent, version 2.4.3.
Fixed Issues
This release contains the following fixed issues:
-
Fixed connection issues when using an encrypted proxy password stored in mule-agent.yml.
For information, see Include an Encrypted Password in the mule-agent.yml File.
-
Fixed an issue in which a persistent Object Store that was created with its connector was deleted when redeploying and restarting an app through Runtime Manager. (MULE-17300, MULE-17417)
To take advantage of this fix, you must also upgrade your Mule runtime engine to version 4.3.0. See Mule Runtime 4.3.0 Release Notes.
2.4.2
September 3, 2019
These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent, version 2.4.2.
2.4.1
July 26, 2019
These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent, version 2.4.1.
2.4.0
July 22, 2019
These are the new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager agent, version 2.4.0.
New Features and Enhancements
This release contains the following new features or enhancements:
-
Atomic schedulers modifications: A new HTTP endpoint in the Mule Runtime Manager agent API will modify schedulers' settings atomically so that other schedulers deployed to the same Mule runtime engine are not triggered. Prior to this update, modifications to schedulers forced the synchronous trigger of the schedulers of all applications running in the same Mule runtime engine.