What would cause MSMQ to place messages destined for queues on the local system into the "Outgoing Queues"? -


MSMQ maintains a type of queue called "Outgoing Cues" The queue messages destined for the server by MSMQ service When used to keep it, it can not be contacted when the message is generated. These special, temporary queues that are different from the general public and private queues.

I have recently encountered a situation where some messages are set for the local system (i.e. the computer that generates the message) in one of the "outgoing quoices" Ends when drilling in outgoing cues with management console can see that the destination has the right path information for local systems and queue. In this special scenario, the messages organized in these "outgoing quotes" are never distributed in the correct queue. Staying there, effectively lost.

Few messages destined for queues on local systems are included for the same queues listed in "outgoing quizzes", are delivered exactly. When messages end in "Outgoing Cues", they seem random. That's it: Some will work fine, others will not do

The queues that are suffering on it are all non-behaviors, transactional queues always receive messages. At least, the sender's application has no exceptions for transaction queues.

What would be the reason for giving a fateful message to the queue in the "outgoing queue" on the local MSMQ? Is it that MSMQ service can not contact itself to send messages? The system is very busy (80% + CPU usage) Should MSMQ be hungry for resources?

I have seen problems with MSMQ in the past to help it in relation to DNS Try putting the fully qualified DNS entry into the C: \ Windows \ System32 \ Drivers \ etc \ HOSTS file.

Not sure why you have a DNS problem, but this help


Comments

Popular posts from this blog

oracle - The fastest way to check if some records in a database table? -

php - multilevel menu with multilevel array -

jQuery UI: Datepicker month format -