Azure的服务总线队列中的消息卡住了 [英] Azure Service Bus queue messages got stuck
问题描述
我最近创建从那里我发送和接收所有的时间划分的一些队列。他们已经运行作为非分区在过去没有任何的我当前的问题。
I recently created some partitioned queues from where I send and receive all the time. They've run as non-partitioned in the past without any of my current issues.
问题是，我在排队，我不能接收消息的数量不变。我总是得到任何回报不发送任何其他消息队列的时候，但是当我将消息发送到队列中，我收到了新邮件没有问题。被滞留在队列中的消息是活动消息，没有死字母。
The problem is, I have a constant number of messages in the queue that I can not receive. I always get nothing back when not sending any other messages to the queues but when I send messages to the queues I receive the new messages without a problem. The messages that are stuck in the queue are active messages, not dead lettered.
我怀疑他们被困在一个特定的分区，但我不知道该怎么接待他们。
I'm suspecting they're stuck in a specific partition(s) but I don't know how to receive them.
既然不能接收这些信息是有办法重置ServiceBus队列？
Since I cannot receive these messages is there way to reset the ServiceBus Queue?
任何想法？
更新：
的数量不是恒定的，但非常缓慢增加。在我们的测试环境，我们收到每小时队列略多于2000的消息，被重置为0（零）已收到各地各20条消息在过去的12小时后。这些消息都只是有，但不能接收。至少不以通常的方式
The number is not constant but very slowly increasing. On our testing environment we receive little more than 2000 messages per hour and the queues, after being reset to 0 (zero) has received around 20 messages each in the last 12 hours. Those messages are just there but not receivable. At least not in the usual way.
问题仅在两个命名空间，他们被分区后。问题并不在我们的生活环境中，我们不使用分区队列。
The issue is only in two namespaces after they have been partitioned. The issue is not in our live environment where we don't use partitioned queues.
推荐答案
我见过类似的事情在我们的生产ENV - 也许它相同的行为，你所看到的。使用ServiceBusExplorer或类似的东西，检查邮件的的ContentType =应用程序/ vnd.ms-servicebus平。
I have seen a similar thing in our production env - maybe its the same behavior you are seeing. Using ServiceBusExplorer or something similar, check if the message's 'ContentType' = application/vnd.ms-servicebus-ping.
如果这样......这是生成的消息，以确定队列可用性（天青）系统作为......据我所知，这些消息都应该在接收后消失......但我的也不会。从MS文档是稀疏这个东西...
If so... this is a (Azure) system generated message to determine queue availability... as far as I know these messages are supposed to disappear after they are received... but mine do not either. The documentation from MS is sparse on this stuff...
在任何情况下，如果您确保这是原因，你至少可以放心，他们不是被卡在ServiceBus炼狱邮件。希望不久MS修复此...
In any case, if you make sure that this is the cause, you can at least rest assured that they are not YOUR messages that are stuck in ServiceBus purgatory. Hopefully MS fixes this soon...
这篇关于Azure的服务总线队列中的消息卡住了的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
