Rate Limiting

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.

Rate limit window is no longer limited to 24 days.

Flex support for the Policy.

Quota is now reset when editing tier configuration.

Improved error handling for connectivity issues in clusters.

Improved logging for errors.

Error handling responses revised for WSDL APIs to be compliant 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 resiliency on cluster scenarios.

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

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

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

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

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

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

Optimized the threading usage of the algorithm

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

Several performance improvements were introduced in this release.

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.

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

Fixed NullPointerException thrown when disposing policy in a Mule Cluster.

Resolved the WSDL error response issue.

An object store error occurred when hitting the API concurrently. This error is now resolved.

Optimized throttling connector performance.

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

Added 'violationCategory' in the YAML configuration file for Feedback Loop.

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

Parameterized throttling algorithm introduced for Mule 4.

Migrated pluggable Hazelcast to 4.x.

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

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