Runtime Manager Agent 2.2.x Release Notes

The API now returns the root cause when an application fails to deploy.

Application properties are now stored in the application yml descriptor instead of in the mule-agent.yml.

For APCE environments, trusted certificates are always used from the JKS file instead of the JVM.

Application fails at restart from side panel due to property not found.

When tracking was enabled in Mule 4.1.x, TransactionNotification related errors were written to the application’s log instead of the mule_ee.log.

Support for the host property in CloudHub properties caused applications to fail to deploy.

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

The issue that caused an NPE when processing ExceptionNotification from the implicit error handler is fixed.