Azure Function中SendMessageAsync与CompleteMessageAsync事务异常求助

异常原因 #

出现"Transaction hasn't been declared yet, or has already been discharged"异常的核心原因是：手动创建的TransactionScope与Azure Functions ServiceBus触发器的内置事务上下文冲突。触发器已为messageActions操作提供事务环境，嵌套额外事务会导致CompleteMessageAsync执行时，原事务上下文被错误释放或未关联。

跨实体事务（发送新消息到另一Topic + 完成当前消息）无需手动创建事务，只需让ServiceBus客户端参与到触发器的内置事务中即可。

修复方案 #

1. 移除手动TransactionScope：删除代码中嵌套的事务块，避免与触发器内置事务冲突。
2. 保留跨实体事务配置：ServiceBusClientOptions的EnableCrossEntityTransactions = true配置正确，它会自动将发送消息的操作纳入触发器的事务上下文。
3. 依赖触发器事务自动管理：函数无异常完成时，触发器自动提交事务（完成当前消息+确认新消息发送）；抛出异常时，事务自动回滚（当前消息重新投递，新消息发送撤销）。

修改后完整代码 #

public class Function1
{
    [FunctionName("Function1")]
    public async Task Run(
        [ServiceBusTrigger("%ServiceBusTopicName%", "%ServiceBusSubscriptionName%", Connection = "ServiceBusConnectionString", IsSessionsEnabled = true)]
        ServiceBusReceivedMessage message,
        ServiceBusMessageActions messageActions,
        ILogger log)
    {
        string serviceBusConnectionstring = Environment.GetEnvironmentVariable("ServiceBusConnectionString");
        string aiTopicName = Environment.GetEnvironmentVariable("ServiceBusAITopicName");
        var requestKey = 1;
        var threadKey = 1;

        log.LogInformation($"C# ServiceBus topic trigger function processed message: {message.MessageId}");
        
        // 启用跨实体事务，让sender操作加入触发器的内置事务
        ServiceBusClientOptions options = new() { EnableCrossEntityTransactions = true };
        await using var serviceBusClient = new ServiceBusClient(serviceBusConnectionstring, options);
        ServiceBusSender sender = serviceBusClient.CreateSender(aiTopicName);

        string jsonString = $@"{{""thread_key"": {threadKey}, ""request_key"": {requestKey}}}";
        log.LogInformation(jsonString);

        try
        {
            ServiceBusMessage msg = new ServiceBusMessage(jsonString)
            {
                SessionId = threadKey.ToString()
            };

            await sender.SendMessageAsync(msg);
            log.LogInformation("Connector Processor: SendMessageAsync completed");

            await messageActions.CompleteMessageAsync(message);
            log.LogInformation("Connector Processor: CompleteMessageAsync completed");
        }
        catch (Exception ex)
        {
            string errorMessage = ex.Message;
            log.LogError("Connector Processor: Exception: {Message}", errorMessage);

            if (ex.InnerException != null)
            {
                errorMessage += " | Inner Exception: " + ex.InnerException.Message;
                log.LogError("Connector Processor: Full Exception: {Message}", errorMessage);
            }

            // 异常时手动放弃消息以触发重试（根据业务需求调整）
            try
            {
                await messageActions.AbandonMessageAsync(message);
                log.LogInformation("Connector Processor: Message abandoned for retry");
            }
            catch (Exception abandonEx)
            {
                log.LogError("Connector Processor: Failed to abandon message: {Message}", abandonEx.Message);
            }
        }
    }
}

额外注意事项 #

• host.json配置验证：确保ServiceBus触发器的事务功能启用（默认已启用，若有修改需检查）：

{
  "version": "2.0",
  "extensions": {
    "serviceBus": {
      "transactionProcessing": {
        "enabled": true
      }
    }
  }
}

• 会话一致性：目标Topic的订阅需启用会话，否则带SessionId的消息无法被正常接收。
• 异常处理逻辑：无特殊业务需求时，无需手动调用AbandonMessageAsync，触发器会自动处理消息的重试或死信；如需自定义重试逻辑，再添加手动放弃逻辑。

内容的提问来源于stack exchange，提问作者Indian songs comedy jolly use