Runtime Manager Agent 2.2.x Release Notes
February 19, 2019
This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager Agent, version 2.2.1.
The API now returns the root cause when an application fails to deploy.
Application properties are now stored in the application
ymldescriptor instead of in the
For APCE environments, trusted certificates are always used from the JKS file instead of the JVM.
This release contains the following fixed issues:
Application fails at restart from side panel due to property not found.
When tracking was enabled in Mule 4.1.x,
TransactionNotificationrelated errors were written to the application’s log instead of the
Support for the
hostproperty in CloudHub properties caused applications to fail to deploy.
January 28, 2018
This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager Agent, version 2.2.0.
This release contains the following new features or enhancements:
Added Java 11 OpenJDK Support
This version of Runtime Manager Agent enables connection to the new Runtime Manager Publicly Certified endpoints for Mule Manager and Auth Proxy.
Now, when enabling a service that has a null log configuration, the Mule Agent API returns a bad request (400) instead of an internal server error (500).
This release contains the following fixed issue:
The issue that caused an NPE when processing
ExceptionNotificationfrom the implicit error handler is fixed.
When you upgrade the agent, two new endpoints for communicating with Anypoint Runtime Manager are created.
Before performing the upgrade, ensure there are no networking constraints for accessing the FQDNs on port 443. For more information, see Ports, IP Addresses, and Hostnames to Allowlist.