Azure Service Bus句柄配额超限（4999）问题的解决步骤咨询

异常信息 #

Cannot allocate more handles. The maximum number of handles is 4999. (QuotaExceeded)

堆栈跟踪：
at Azure.Messaging.ServiceBus.Amqp.AmqpConnectionScope.CreateSendingLinkAsync(String entityPath, String identifier, AmqpConnection connection, TimeSpan timeout, CancellationToken cancellationToken)
at Azure.Messaging.ServiceBus.Amqp.AmqpConnectionScope.OpenSenderLinkAsync(String entityPath, String identifier, TimeSpan timeout, CancellationToken cancellationToken)
at Azure.Messaging.ServiceBus.Amqp.AmqpSender.CreateLinkAndEnsureSenderStateAsync(TimeSpan timeout, CancellationToken cancellationToken)
at Microsoft.Azure.Amqp.FaultTolerantAmqpObject1.OnCreateAsync(TimeSpan timeout) at Microsoft.Azure.Amqp.Singleton1.GetOrCreateAsync(TimeSpan timeout)
at Microsoft.Azure.Amqp.Singleton1.GetOrCreateAsync(TimeSpan timeout) at Azure.Messaging.ServiceBus.Amqp.AmqpSender.CreateMessageBatchInternalAsync(CreateMessageBatchOptions options, TimeSpan timeout) at Azure.Messaging.ServiceBus.Amqp.AmqpSender.<>c.<CreateMessageBatchAsync>b__16_0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at Azure.Messaging.ServiceBus.ServiceBusRetryPolicy.RunOperation[T1,TResult](Func4 operation, T1 t1, TransportConnectionScope scope, CancellationToken cancellationToken)
at Azure.Messaging.ServiceBus.ServiceBusRetryPolicy.RunOperation[T1,TResult](Func`4 operation, T1 t1, TransportConnectionScope scope, CancellationToken cancellationToken)
at Azure.Messaging.ServiceBus.Amqp.AmqpSender.CreateMessageBatchAsync(CreateMessageBatchOptions options, CancellationToken cancellationToken)
at Azure.Messaging.ServiceBus.ServiceBusSender.CreateMessageBatchAsync(CreateMessageBatchOptions options, CancellationToken cancellationToken)

解决步骤 #

1. 复用ServiceBusClient实例 #

• 每个Azure Function实例中禁止每次请求创建新的ServiceBusClient，它是线程安全的，应作为单例复用。可通过静态构造函数初始化，或依赖注入注册为单例：

// 静态单例实现示例
private static readonly ServiceBusClient _serviceBusClient = new ServiceBusClient("your-connection-string");

[FunctionName("SendToTopicFunction")]
public async Task Run([HttpTrigger(AuthorizationLevel.Function, "post")] HttpRequest req, ILogger log)
{
    var sender = _serviceBusClient.CreateSender("target-topic");
    // 消息发送逻辑
}

• ServiceBusClient会自动管理连接与链接复用，大幅降低句柄消耗。

2. 限制单连接的并发链接数 #

• 通过ServiceBusClientOptions配置单连接的最大并发链接数，避免无限制创建发送链接：

var clientOptions = new ServiceBusClientOptions
{
    Amqp = new AmqpTransportSettings
    {
        // 根据业务场景调整，建议设置为100-200区间
        MaxLinksPerConnection = 150
    },
    // 闲置连接自动超时释放，减少无效句柄占用
    ConnectionIdleTimeout = TimeSpan.FromMinutes(3)
};
var serviceBusClient = new ServiceBusClient("your-connection-string", clientOptions);

3. 批量发送消息 #

• 避免单条发送消息，改用批量发送减少发送链接的创建频率：

using var sender = _serviceBusClient.CreateSender("target-topic");
using var batch = await sender.CreateMessageBatchAsync();

foreach (var messageContent in messageList)
{
    var serviceBusMsg = new ServiceBusMessage(messageContent);
    if (!batch.TryAddMessage(serviceBusMsg))
    {
        // 当前批次已满，先发送
        await sender.SendMessagesAsync(batch);
        // 创建新批次继续添加
        batch = await sender.CreateMessageBatchAsync();
        batch.TryAddMessage(serviceBusMsg);
    }
}
// 发送剩余消息
await sender.SendMessagesAsync(batch);

4. 优化Azure Functions并发配置 #

• 在host.json中调整函数并发数，避免过多并发实例同时创建发送链接：

{
  "version": "2.0",
  "extensions": {
    "functions": {
      // 根据服务器资源情况降低并发请求数
      "maxConcurrentRequests": 80
    }
  }
}

• 若使用消耗计划，通过应用设置WEBSITE_MAX_DYNAMIC_APPLICATION_SCALE_OUT限制动态扩缩容的实例数量。

5. 及时释放资源 #

• 使用using语句确保ServiceBusSender和ServiceBusMessageBatch在使用后及时释放，避免资源泄漏：

using var sender = _serviceBusClient.CreateSender("target-topic");
using var batch = await sender.CreateMessageBatchAsync();
// 执行发送逻辑

6. 检查并升级Service Bus配额 #

• 登录Azure门户查看Service Bus命名空间的连接数、链接数配额，若已达上限，可升级命名空间层级（如从基础层升级至标准/高级层），高级层支持更高的配额上限。

内容的提问来源于stack exchange，提问作者Dev