Hi everyone,
We’ve just released NServiceBus.Transport.AzureServiceBus 4.2.0.
Improvements/Features
- #1023 Fallback to individual sends when batching is not possible
Fixed bugs
- #994 An endpoint is “force detached” by the broker when sending messages
How to know if you are affected
You are affected if:
- you use the Premium Tier of Azure Service Bus with large message support and the total size of messages sent in a batch exceeds the assigned size limit.
- you are sending messages where the size of a single message exceeds the maximum size allowed for a batch
Symptoms
You observe one of the following exceptions:
> System.InvalidOperationException: The link 'G6:14740510:amqps://**namespace removed**.servicebus.windows.net/-dd910ad4;0:7:8' is force detached by the broker because publisher(link3082) received a batch message with no data in it. Detach origin: Publisher.
For troubleshooting information, see https://aka.ms/azsdk/net/servicebus/exceptions/troubleshoot.
> Unable to add the message '#0' with message id '{ID}' to the the batch '#{x}'.
The message may be too large or the batch size has reached the maximum allowed messages per batch for the current tier selected for the namespace '{NAMESPACE}'.
To mitigate this problem reduce the message size by using the data bus or upgrade to a higher Service Bus tier. (MessageSizeExceeded). For troubleshooting information, see https://aka.ms/azsdk/net/servicebus/exceptions/troubleshoot.
When to upgrade
If you are affected, you should upgrade immediately. Otherwise, upgrade during your next maintenance window.
Where to get it
You can install NServiceBus.Transport.AzureServiceBus 4.2.0 from NuGet.
Please read our release policy for more details.
With thanks,
The team in Particular