Runtime Manager Agent 1.9.x Release Notes

Upgrades the Jackson library to version 2.9.5 to fix vulnerability.

Upgrades Jetty to version 9.4.8.v20171121 to fix vulnerability.

Fixes error when tracking notification were consumed and sent to a database.

Added log entries for web socket disconnections to help understand the root cause of server disconnections.

Reduced logging verbosity of the Runtime Manager Agent to avoid unnecessary log noise

Add runtime version and agent version to response of the endpoint to retrieve information about the agent and the runtime.

Upgrade amc_debug script to exclude HEAP by default and include network check.

Support for Schedule Management on Clusters and Server Groups

Upgrade BouncyCastle library to 1.59 to fix vulnerability (CVE-2017-13098)

Fix bug in scheduling management where not all schedulers where being reported when the agent had schedulers configured.

Added support for the EU control plane.

Added correlationSequence and correlationGroupSize to the event tracking notification.

Added the ability to collapse comments.

Added a check for application properties feature availability.

Made the command line agent installer URLs take precedence over the service registry ones.

Upgraded the log4j library from 2.5 to version 2.8.2 due to end of support and vulnerability(CVE-2017-5645).

Upgraded the Grizzly library version due to security vulnerability(CVE-2017-1000028).

Ensured that null application properties are not applied at deployment/redeployment time.

Updated runtime status displayed in Runtime Manager to CONNECTED when the runtime is boot instead of when the application starts. This resolve an issue with servers experiencing disconnection issues when an application took longer than 50 seconds to start.

Fixed issue where application properties managed in Runtime Manager did not default to the correct values.

Changed the log level in situations when JMX is not found.

Fixed issue where Memory Server Metrics were not being collected correctly when configuring a different garbage collector in the wrapper.conf file.

Fixed issue with FileNotFoundException after installing the RUagent with -I flag.

[SE-6934] Fixed issue where global flags were not being considered when they were not set for trackedApplication.

[SE-6307] Fixed issue where the Runtime Manager Agent failed to work on the IBM JDK.

Added support for deploying applications to regions within the European Union. Update: Due a change in the SSL certificates, 1.9.1 has NO longer support for the European Union region. Please use the 1.9.2 and above version of the Mule Agent for that region’s support.

Fixed issue where a user could not delete an application that failed to deploy.

Fixed issue where a custom business event name was not displayed in Insights.

Fixed issue where Mule agent fails on the IBM JDK.

Added support for Autodiscovery of local Server Properties.

Added support for Configuration Management when deploying or redeploying.

Mule Runtime Agent support for schedulers management

Support for multiple environments on Anypoint Platform

Support for Mule Runtime Agent configuration fragments

Support for large application sizes (200MB)

MuleAgentProperties are now stored in wrapper.conf

Corrected response when listing apps from Rest API

Updated dependency versions

Runtime Manager Agent

Install or Update the Runtime Manager Agent