Azure/azure-sdk-for-net Azure.Messaging.EventHubs.Processor

5.3.1 (2021-03-09)

Fixed an issue where long-lived credentials (more than 49 days) were overflowing refresh timer limits and being rejected.
Added detection and recovery for a race condition that occurred when the Event Hubs service closed a connection or link after the client had validated its state and was performing an operation; this will now be properly retried with a fresh connection/link.
Extended retry scenarios to include generic I/O exceptions, as they are typically transient network failures.
Extended retry scenarios to include authorization failures, as the Event Hubs services do not differentiate between authentication and authorization, callers cannot reason about whether an Unauthorized return from an operation indicates that the call will never succeed or may trigger a credential renewal that may allow success.