FÖRSÄLJNING: 1-800-867-1389
EN
Det här innehållet finns inte tillgängligt på ditt språk men här finns den engelska versionen,

Service Bus Quotas

Updated: August 27, 2014

This section enumerates basic quotas and throttling thresholds in Microsoft Azure Service Bus messaging.

The maximum number of service namespaces allowed per account is 50.

For information about other quotas for Service Bus, see the Azure Platform pricing FAQ.

The following table lists quota information specific to Service Bus:

TipTip
Having trouble viewing this topic in the 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/subscription 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.

2,000

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

The total number of topics plus queues in a service namespace must be less than or equal to 10,000.

Number of partitioned topics/queues per service namespace

System-wide

Static

Subsequent requests for creation of a new partitioned 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, a QuotaExceededException exception will be received by the calling code.

100

Each partitioned queue or topic counts towards the quota of 10,000 entities per namespace.

Maximum size of queue or topic names

Entity

Static

50 characters

Maximum size of Event Hubs (Preview) event

System-wide

Static

256 KB

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: 256KB

noteNote
Due to system overhead, this limit is usually slightly less than 256KB.

Maximum header size: 64KB

Maximum 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 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.

Var detta till hjälp?
(1500 tecken kvar)
Tack för dina kommentarer
Visa:
© 2014 Microsoft