是什么会导致MSMQ将发往本地系统上队列的消息放入“传出队列"? [英] What would cause MSMQ to place messages destined for queues on the local system into the "Outgoing Queues"?

问题描述

MSMQ维护一种称为传出队列"的队列. MSMQ服务使用这些队列来保存发往该消息生成时无法联系的服务器的消息.这些是特殊的临时队列，与普通的公共"和专用"队列分开.

MSMQ maintains a type of queue called "Outgoing Queues". These queues are used by the MSMQ service to hold messages destined for servers that it cannot contact when the message is generated. These are special, temporary queues that are separate from the normal Public and Private queues.

我最近遇到了一种情况，其中某些发往 local 系统的消息(即生成消息的同一台计算机)最终出现在传出队列"之一中.使用管理控制台深入到发送队列"时，可以看到目标具有本地系统和队列的正确路径信息.在这种特定情况下，这些传出队列"中保存的消息永远不会传递到正确的队列中.那里的其余人实际上丢失了.

I've recently encountered a scenario where some messages destined for the local system (i.e. the same computer that generated the message) end up in one of the "Outgoing Queues". When drilling into the Outgoing Queues with the Management Console one can see that the destination has the correct path information for the local system and the queue. In this particular scenario, the messages that are held in these "Outgoing Queues" are never delivered to the correct queue. The remain there, effectively lost.

一些发往本地系统上队列的消息，包括传出队列"中列出的相同队列的消息，可以很好地传递.当消息最终出现在传出队列"中时，似乎是随机的.那就是:有些可以正常工作，有些则不能.

Some messages destined for queues on the local system, including ones for the same queues listed in the "Outgoing Queues", are delivered just fine. When messages end up in the "Outgoing Queues" seems to be random. That is: some will work fine, others will not.

似乎受此困扰的队列都是非事务性的.事务性队列似乎总是接收消息.至少，发送消息的应用程序没有捕获到事务队列的异常.

The queues that seem to be afflicted by this are all non-transactional. Transactional queues always seem to receive messages. At least, the application sending the message has not captured an exception for transactional queues.

什么会导致MSMQ将发往本地系统上队列的消息放入传出队列"?是MSMQ服务无法联系自身来发送消息吗?系统非常忙(CPU使用率超过80％).这样做会导致MSMQ缺乏资源吗?

What would cause MSMQ to place messages destined for queues on the local system into the "Outgoing Queues"? Is it that the MSMQ service cannot contact itself to send the message? The system is pretty busy (80%+ CPU usage). Could MSMQ be starved for resources when it does this?

推荐答案

我过去曾见过与DNS有关的MSMQ问题.尝试将完全合格的DNS条目放入C:\ Windows \ System32 \ Drivers \ etc \ HOSTS文件中，以查看是否有帮助.

I've seen issues with MSMQ in the past in relation to DNS. Try putting a fully qualified DNS entry in the C:\Windows\System32\Drivers\etc\HOSTS file to see if it helps.

不确定在这里为什么会有DNS问题，但这可能会有所帮助.

Not sure why you'd have a DNS issue here, but it may help.

这篇关于是什么会导致MSMQ将发往本地系统上队列的消息放入“传出队列"?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！