Message batching: remove/provide max number of messages per batch

[MiYanni]

Description

There is a hardcoded limit of 4500 messages per batch. Currently, this isn't documented and does not provide a reasonable error message. The request is to either remove the max message count limit or provide the max message count limit as a property on the link so clients (such as Azure SDKs) are aware of the limit during runtime.

Edit: After additional testing, it seems that Basic and Standard are 4500. Premium seems to be ~15885. Based on there being different amounts per service tier, we recommend that the limits be documented with the rest of the quotas for the service.

Actual Behavior

1. Add more than 4500 messages to a batch and attempt to send it (Basic or Standard tier).
2. Error returned is: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101

Expected Behavior

1. Add more then 4500 message to a batch and attempt to send it (Basic or Standard tier).
2. Service clients are able to know (dynamically) the message limit per batch on a link. They will either allow or deny adding this message to the batch based on the constraints the link provides. If the constraints are removed entirely from the service, then the batch limit is only based on the size of the batch and not the count of messages.

Related issues: https://github.com/Azure/azure-service-bus/issues/396 https://github.com/Azure/azure-service-bus-dotnet/issues/538

[SeanFeldman]

this isn't documented and does not provide a reasonable error message.

If you don't mind, how did you find it out? Thank you.

[MiYanni]

@SeanFeldman I tried to send 50k messages in a batch for a stress test for the C# SDK (Track 2). I progressively reduced the number of messages until I found out that I could not send 4501 messages in a batch, but 4500 worked.

[mxa0079]

Any updates? This issue seems to be abandoned.

[MiYanni]

@mxa0079 I don't work for this team anymore. Let me see if someone else knows...

@jsquire Do you know who would be looking at an issue like this?

[jsquire]

This falls under the Service Bus team. @EldertGrootenboer would be most likely to have insight.

[EldertGrootenboer]

We have assigned an engineer to look into this.

[giulianabaratto]

Any news on this subject?

[EldertGrootenboer]

Thank you for your feedback. We have brought this item in our current semester, and should be able to provide an update in the coming months.