已声明为非独占的RabbitMQ队列仍被锁定，求排查原因

问题描述 #

我使用RabbitMQ的.NET客户端实现RPC模式，为避免服务端或客户端未启动时消息丢失，双方采用相同参数声明队列。但客户端声明队列时抛出OperationInterruptedException异常：

operation queue.declare caused a channel exception resource_locked: cannot obtain exclusive access to locked queue '151' in vhost '/'. It could be originally declared on another connection or the exclusive property value does not match that of the original declaration.

尝试过类似问题的解决方案但无效，.NET客户端的BasicConsumer默认是非独占的。仅在服务端声明队列时代码可正常运行，但我不想强制要求服务端必须先于客户端启动。

核心问题：双方均未将队列声明为独占，为何会出现该异常？

简化代码示例 #

客户端代码 #

public MyClient(){
    try {
        ConnectionFactory factory = new() {
            HostName = "localhost"
        };
        IConnection connection = factory.CreateConnection();
        channel = connection.CreateModel();
        sendUpdatesMessenger = new("sendUpdates", channel);
        getUpdatesMessenger = new("getUpdates", channel);
        getUpdatesReceiver = new("getUpdates", "localhost", channel);
        sendUpdatesReceiver = new("sendUpdates", "localhost", channel);
        string bodyStr = "test example string";
        string messageId = new Guid().ToString();
        bool success = getUpdatesMessenger.SendMessage(messageBody: bodyStr, routingKey: "151", correlationId: messageId, replyQueue: "myReplyQueue");
        // 根据success结果处理后续逻辑
    } catch (Exception ex){
        Debug.WriteLine("Exception " + ex);
    }
}

public bool SendMessage(string messageBody, string routingKey, string correlationId, string replyQueue = ""){
    try{
        IBasicProperties props = channel.CreateBasicProperties();
        props.CorrelationId = correlationId;
        props.ReplyTo = replyQueue;
        channel.QueueDeclare(queue: routingKey, durable: true, exclusive: false, autoDelete: false);
        channel.BasicPublish(exchange: exchange, routingKey: routingKey, basicProperties: props, body: Encoding.ASCII.GetBytes(messageBody));
        return true;
    }
    catch(Exception ex){
        Debug.WriteLine("Error: " + ex);
        return false;
    }
}

服务端代码 #

public bool BindQueue(string routingKey){
    try {
        channel.QueueDeclare(queue: routingKey, durable: true, autoDelete: false);
        channel.QueueBind(queue: routingKey, routingKey: routingKey, exchange: exchangeName);
        queueNames.Add(routingKey);
        return true;
    }
    catch (Exception ex){
        Console.WriteLine(ex);
        return false;
    }
}

异常原因与解决方案 #

原因分析 #

问题出在服务端与客户端的队列声明参数不完全一致：
客户端的QueueDeclare显式指定了exclusive: false，但服务端调用QueueDeclare时省略了exclusive参数。在RabbitMQ .NET客户端中，该重载的exclusive默认值为true。

这会导致：若服务端先启动，会以exclusive: true创建独占队列；后续客户端用exclusive: false声明同名队列时，因独占队列仅允许声明它的连接访问，其他连接无法以非独占方式复用，从而触发resource_locked异常。

解决方案 #

修改服务端的QueueDeclare调用，显式设置所有参数与客户端完全匹配：

public bool BindQueue(string routingKey){
    try {
        // 显式指定exclusive: false，与客户端参数保持一致
        channel.QueueDeclare(queue: routingKey, durable: true, exclusive: false, autoDelete: false);
        channel.QueueBind(queue: routingKey, routingKey: routingKey, exchange: exchangeName);
        queueNames.Add(routingKey);
        return true;
    }
    catch (Exception ex){
        Console.WriteLine(ex);
        return false;
    }
}

额外说明 #

RabbitMQ的队列声明具有幂等性，但前提是所有声明参数（durable、exclusive、autoDelete、arguments等）完全一致。只要确保客户端与服务端的QueueDeclare参数完全相同，就能实现任意一方先启动都不会出现异常。

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