Rate Limiting - SLA-based

The policy definition and policy implementation file are now separate. This enables stronger validations for policy configuration parameters.

Nodes no longer become unresponsive on a cluster scenario when persistence is enabled.

Flex support for the Policy.

Improved error handling for connectivity issues in clusters.

Improved logging for errors.

Corrected spelling issues and typos in policy’s code snippets.

Added OAS 3.0 code snippet in the policy YAML file.

Error handling responses revised for WSDL APIs to be compilant with SOAP 1.1 and 1.2.

Performance improvements are introduced to the header manipulation engine.

After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity:

Improved logging information in locking, object store, and distributed mechanisms for better troubleshooting.

Added client name in the authentication attributes for the request to an API that has the Rate Limiting policy applied.

When request quota exceeds, authentication objects are now made accessible to the protected resource in the authentication store.

Several performance improvements were introduced in the algorithm of the Rate Limiting policy.

Improved algorithm to allow executing with small throttling.distribution_percentage values.

Removed the warning (WARN) message in application log when multiple async quota requests are executed in a distributed scenario.

Fixed the NullPointerException error on persistence scheduler when distributed quota is temporarily unavailable.

Improved resiliency when throttling algorithm is created under heavy load in clustering scenarios.

Optimized the threading usage of the algorithm.

Fixed the NullPointerException error on persistence scheduler when counters are persisted due to a sudden surge in requests.

Several performance improvements were introduced in this release.

The persistence scheduler was losing quota in a Mule Cluster when the node’s clocks were out-of-sync. This error is not resolved.

An error occurred when multiple client applications using one rate limiting algorithm were configured with the same SLA in Anypoint Platform. This error is now resolved.

Unless explicitly configured, by checking the "Expose headers" option, the policy header will not be propagated or returned. The default configuration is modified to support this behaviour.

Several performance improvements were introduced in this release.

Fixed NullPointerException thrown when disposing policy in a Mule Cluster.

Improved the RAML and OAS snippets.

Migrated pluggable Hazelcast to 4.x.

The Rate Limiting policy was rejected from scheduler during high network traffic. This error is now resolved.

An ExpressionRuntimeException error occurred when a WSDL proxy received an empty payload, or an invalid XML. This error is now resolved.

If an extension set authentication using an Authentication object containing null properties, a NullPointerException error occurred. This error is now resolved.

Changed WWW-Authenticate header value from mule-real to Client-ID-Enforcement.

Reduced error-handling verbosity in templates.

An ExpressionRuntimeException error occurred when a WSDL proxy received an empty payload, or an invalid XML. This error is now resolved.