Dapr Azure Service bus Exception when amqp:resource-limit-exceeded

[halspang]

Note: Issue contents copied from https://github.com/dapr/dotnet-sdk/issues/879 since I can't move the issue itself.

Expected Behavior

When the Azure service bus reaches its max limit, this exception occurs for publishing messages.. Dapr.DaprException: Publish operation failed: the Dapr endpoint indicated a failure. See InnerException for details. ---> Grpc.Core.RpcException: Status(StatusCode="Internal", Detail="error when publish to topic **** in pubsub pubsub: *Error{Condition: amqp:resource-limit-exceeded, Description: The maximum entity size has been reached or exceeded for Topic: 'LSERVICE:TOPIC:****'. Size of entity in bytes:5368710032, Max entity size in bytes: 5368709120. For more information please see https://aka.ms/ServiceBusExceptions

But after processing some messages, when size is less than the max size then, Service bus should accept messages.

Actual Behavior

But even after the topic queue gets empty or the size is below maximum. Dap can not publish the message due to the above error. But if I publish messages directly from .NET SDK then messages are publishing fine. This error goes away only after restarting the specific deployment which is getting this error.

Steps to Reproduce the Problem

When we hit the max size in the Azure service bus. Then this error starts occurring.

Release Note

RELEASE NOTE:FIX Bug in runtime

[addjuarez]

/assign