An <async> scope can now be configured to wait for its in-flight events to finish before flows are stopped during a graceful shutdown, which helps avoid dropped or canceled async work. This behavior is disabled by default and can be enabled through the mule.async.gracefulShutdown.drainInflight system property.
|
|
An SDK-based reconnectable message source no longer attempts to reconnect while a graceful shutdown is in progress.
|
|
Custom error mappings in the Tracing module are no longer lost on error propagation when an operation inside a tracing:with-correlation-id scope fails, which previously reverted the mapped error type to the raw connector error.
|
|
A disposed source policy is no longer left in the policy cache when a flow is stopped and restarted while cache population and flow-stop invalidation occur concurrently.
|
|
A memory leak no longer occurs when parallel-foreach and scatter-gather routes leave the route event pinned in a worker thread’s memory after route completion.
|
|
Artifact descriptor validation failures during deployment now report more specific exceptions.
|
|
A malformed authorization URL no longer occurs when the configured OAuth authorizationUrl contains an existing query parameter.
|
|
The HTTP client configurer now includes a method to control whether sensitive headers are filtered when a request is redirected to a different domain.
|
|
A forward-proxy client no longer sends a malformed, path-only request line.
|
|
A worker thread no longer hangs indefinitely, eventually exhausting the runtime’s thread pool, when a client drops the connection while its HTTP request body is being read.
|
|
Netty-based HTTP client requests no longer fail when the response contains a header section larger than 8 KB and a larger response header size limit is configured.
|
|
DIGEST authentication in the Netty-based HTTP client no longer fails with a 401 Unauthorized response when the server issues an RFC 7616-compliant challenge.
|
|
A NullPointerException no longer occurs during cluster node discovery when using PCF or Kubernetes-based cluster discovery.
|
|
Analytics events for requests rejected due to back-pressure are no longer incorrectly reported as HTTP 500 and now correctly report 503 by default. Custom status codes for other error scenarios can also be configured through the anypoint.platform.error.mapping (format NAMESPACE:IDENTIFIER:STATUS_CODE, comma-separated for multiple mappings) and anypoint.platform.error.default system properties.
|
|
API Gateway no longer fails to read shard checksums from an ETag header that contains commas.
|
|
The fix for idle connections being destroyed and recreated instead of reused when the number of idle connections reached the configured maxIdle limit under concurrent load, introduced in a previous release, is reverted in this release.
|
|
The jsoup library is upgraded to 1.23.1.
|
|
The Netty library is upgraded to 4.2.17.Final.
|
|
The Jackson library is upgraded to 2.22.1.
|
|
The RAML Parser library is upgraded to 2-1.2.1.
|
|
The com.mulesoft.mule.runtime.gw.api.analytics package is now open to all modules, so the Runtime Manager agent can serialize analytics events.
|
|
Worker TLS configuration for Government Cloud is strengthened.
|
|