Service Bus for Windows Server Quotas
Applies To: Service Bus for Windows Server 1.1
The following table lists quota information specific to Service Bus for Windows Server:
Quota Name |
Parameter Name |
Scope |
Type |
Behavior when exceeded |
Service Bus for Windows Server quota |
|---|---|---|---|---|---|
Queue/Topic size |
Maximum-QueueSize-InMegabytes Maximum-TopicSize-InMegabytes |
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, 5, 6, 7, 8, 9, or 10 GB. There is also a maxSize option, which is approximately 8.7961E+9 MB. |
Number of concurrent connections on a queue/topic/subscription entity |
Maximum-Number-OfConnections-PerEntity |
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. |
Unlimited (2^31) |
Number of concurrent receive requests on a queue/topic entity |
Maximum-ConcurrentReceiveRequests-PerEntity |
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 of a topic. |
Unlimited (2^31) |
Number of topics/queues per service namespace |
Maximum-Number-Of-Queues-PerNamespace Maximum-Number-Of-Topics-PerNamespace |
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. |
Unlimited (2^31) |
Message size for a queue/topic/subscription entity |
MaxMessage-Size-InBytes |
System-wide |
Static |
Incoming messages that exceed these quotas will be rejected and an exception will be received by the calling code. |
50 MB |
Message property size for a queue/topic/subscription entity |
Hard-coded |
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 |
MaxSubscriptions |
System-wide |
Static |
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 |
MaxSqlFilters |
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 |
MaxCorrelationFilters |
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 |
Number of properties per correlation filter |
Maximum-NumberOf-PropertiesPer-Correlation-Filter |
System-wide |
Static |
An exception is generated. |
8 |
Size of SQL filters/actions |
Hardcoded |
System-wide |
Static |
An exception is generated. |
Maximum length of filter condition string: 1K. Maximum length of rule action string: 1K. Maximum number of expressions per rule action: 32. |