servicestack ServiceStack RabbitMqRequestReplyTests在DLQ中保留消息

即使测试通过，死信队列中仍有相当多（1 run-43 dlq）消息。下面是一些相互关联的示例

Exchange    mx.servicestack.dlq
Routing Key     mq:Incr.dlq
Redelivered     ○
Properties  
timestamp:  1413840195
message_id: 887b23b8-1243-4e58-9332-0c6cb3af14c6
reply_to:   mq:tmp:916f686feb924d1fb2bfe5b2aa5087d9
priority:   0
delivery_mode:  2
headers:    
Error:  {"ErrorCode":"OperationInterruptedException","Message":"The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=405, text=\"RESOURCE_LOCKED - cannot obtain exclusive access to locked queue 'mq:tmp:916f686feb924d1fb2bfe5b2aa5087d9' in vhost '/'\", classId=50, methodId=20, cause=","Errors":[]}
content_type:   application/json
Payload 12 bytes Encoding: string   

{"Value":41}

---

这个特定消息重复了10次，这是我应该关心的吗？

您程序中的某个东西将队列声明为独占的，因此任何试图访问这些队列的东西都不能，因为队列被声明为独占的

问题在于我忽略了存在的事实！这就是当你有了年迈的孩子时会发生的事情