ServiceStack RabbitMqRequestReplyTests在DLQ中保留消息

Question

即使测试通过，死信队列中也会有很多（1运行 - 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次，这是我应该关注的事情吗？

Answer 1

程序中的某些内容将队列声明为独占，因此无论其他任何尝试访问这些队列的内容都不能，因为队列被声明为独占

Answer 2

问题是我错过了this test存在的事实！这就是当你养老孩子时会发生的事情。