Flex Gateway新着情報
Governance新着情報
Monitoring API ManagerJuly 27, 2019
This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager version 2.11.4.
There are no new features or enhancements in this release.
There are no changes in this release.
SE-12164: Unable to deploy Mule apps type as "Examples" to Runtime Fabric with "message": "The file MUST be a jar to deploy to a 4.X target."
There are no known limitations or workarounds in this release.
There are no upgrade requirements for this release.
There are no compatibility notes in this release.
June 15, 2019
This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager version 2.11.3.
There are no new features or enhancements in this release.
Previous to this release, multiple Mule runtime engines (Mules) sharing the same identity were able to connect to the Anypoint control plane when a connection request happened concurrently.
Starting with this release, only one Mule is allowed to connect to the control plane per server. Concurrent Mule connections will no longer be allowed to connect and provide status, which means all but one of the concurrent Mules will become unmanaged.
The Mule that connects first is able to send information over and sync (in some cases this can mean re-deploying applications that are not actually running on the connected Mule). If the initial Mule then becomes disconnected, there is the potential that the other Mules may connect before the initial Mule can re-connect. This means that the sync process occurs from the current state of the newly connected Mule.
This change is beneficial to prevent the possibility of:
Multiple instances of an application running across two or more Mule runtime engines unintentionally
Inaccurate statuses for the Mule runtime engine and/or applications
The issue where multiple connections of different Mule runtime engines were accepted with the same certificate in certain scenarios.
Hybrid scheduler is removed after the flow name changes. [SE-11484]
Unable to add email address starts with # in alert configuration. [SE-11733].
Unable to create a cluster from the UI when runtimes don’t report IP addresses. [SE-12000]
There are no known limitations or workarounds in this release.
There are no upgrade requirements for this release.
There are no compatibility notes in this release.
May 18, 2019
This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager version 2.11.2.
There are no new features or enhancements in this release.
This release contains no feature changes.
The issue where orphan deployments were left in the database when concurrent deployment requests were executed is fixed.
There are no known limitations or workarounds in this release.
There are no upgrade requirements for this release.
There are no compatibility notes in this release.
May 4, 2019
This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager version 2.11.1.
There are no new features or enhancements in this release.
This release contains no feature changes.
Expired Cert incorrect error message when trying to renew certificates for a cluster with an invalid Runtime Manager agent version
There are no known limitations or workarounds in this release.
There are no upgrade requirements for this release.
There are no compatibility notes in this release.
Mar 23, 2019
This document describes new features and enhancements, known limitations, issues, and fixes in Anypoint Runtime Manager version 2.11.0.
Environment information is now being sent to Audit Log for Hybrid Deployments.
This release contains no feature changes.
SE-10644: Re-deployment fails in hybrid with "Duplicate key polling://snippet-pollerFlow/" error
There are no known limitations or workarounds in this release.
There are no upgrade requirements for this release.
There are no compatibility notes in this release.