Windows Azure Service Bus Quotas
This section enumerates basic quotas and throttling thresholds in Windows Azure Service Bus messaging.
General Quotas
The maximum number of service namespaces allowed per Windows Azure account is 50.
For information about other quotas for the Windows Azure Service Bus, see the Windows Azure Platform pricing FAQ.
Messaging Quotas
The following table lists quota information specific to the Service Bus:
Tip |
|---|
| Having trouble viewing this topic in the Windows Azure library? Try viewing it in the MSDN library. |
| Quota Name | Scope | Type | Behavior when exceeded | Value |
|---|---|---|---|---|
|
Queue/Topic size |
Entity |
Defined upon creation of the queue/topic. |
Incoming messages will be rejected and an exception will be received by the calling code. |
1,2,3,4 or 5 Gigabytes. |
|
Number of concurrent connections on a queue/topic/subscription entity |
Entity |
Static |
Subsequent requests for additional connections will be rejected and an exception will be received by the calling code. REST operations do not count towards concurrent TCP connections. |
100 |
|
Number of concurrent receive requests on a queue/topic entity |
Entity |
Static |
Subsequent receive requests will be rejected and an exception will be received by the calling code. This quota applies to the combined number of concurrent receive operations across all subscriptions on a topic. |
5,000 |
|
Number of concurrent listeners on a relay |
Entity |
Static |
Subsequent requests for additional connections will be rejected and an exception will be received by the calling code. |
25 |
|
Number of concurrent relay listeners |
System-wide |
Static |
Subsequent requests for additional connections will be rejected and an exception will be received by the calling code. |
2000 |
|
Number of concurrent relay connections per all relay endpoints in a service namespace |
System-wide |
Static |
|
5,000 |
|
Number of relay endpoints per service namespace |
System-wide |
Static |
|
10,000 |
|
Number of topics/queues per service namespace |
System-wide |
Static |
Subsequent requests for creation of a new topic or queue on the service namespace will be rejected. As a result, if configured through the management portal, an error message will be generated. If called from the management API, an exception will be received by the calling code. |
10,000 |
|
Message size for a queue/topic/subscription entity |
System-wide |
Static |
Incoming messages that exceed these quotas will be rejected and an exception will be received by the calling code. |
Maximum message size: 256KBMaximum header size: 64KBMaximum number of header properties in property bag: MaxValue Maximum size of property in property bag: No explicit limit. Limited by maximum header size. |
|
Message size for Message Buffer |
System-wide |
Static |
Incoming messages that exceed these quotas will be rejected and an exception will be received by the calling code. |
64KB |
|
Message size for NetOnewayRelayBinding and NetEventRelayBinding relays |
System-wide |
Static |
Incoming messages that exceed these quotas will be rejected and an exception will be received by the calling code. |
64KB |
|
Message size for HttpRelayTransportBindingElement and NetTcpRelayBinding relays |
System-wide |
Static |
|
Unlimited |
|
Message property size for a queue/topic/subscription entity |
System-wide |
Static |
A SerializationException exception is generated. |
Maximum message property size for each property is 32K. Cumulative size of all properties cannot exceed 64K. This applies to the entire header of the BrokeredMessage, which has both user properties as well as system properties (such as SequenceNumber, Label, MessageId, and so on). |
|
Number of subscriptions per topic |
System-wide |
Static |
Subsequent requests for creating additional subscriptions for the topic will be rejected. As a result, if configured through the management portal, an error message will be shown. If called from the management API an exception will be received by the calling code. |
2,000 |
|
Number of SQL filters per topic |
System-wide |
Static |
Subsequent requests for creation of additional filters on the topic will be rejected and an exception will be received by the calling code. |
2,000 |
|
Number of correlation filters per topic |
System-wide |
Static |
Subsequent requests for creation of additional filters on the topic will be rejected and an exception will be received by the calling code. |
100,000 |
|
Size of SQL filters/actions |
System-wide |
Static |
Subsequent requests for creation of additional filters will be rejected and an exception will be received by the calling code. |
Maximum length of filter condition string: 1024 (1K). Maximum length of rule action string: 1024 (1K). Maximum number of expressions per rule action: 32. |
Tip