![]() ![]() Messages are stored locally, and the MSMQ service repeatedly attempts to deliver them to the destination queue on the remote machine.Īpproaches for diagnosing messages stuck in the outgoing queue: MSMQ uses store-and-forward to communicate with remote machines. If there are two or more machines with the same QMId, reinstall the MSMQ feature to generate a new QMId. The primary reason for machines ending up with duplicate QMIds is the cloning of virtual machines from a common Windows image without running the recommended Sysprep tool. Which machine works changes in a seemingly random fashion. If two or more machines share the same QMId, only one of those machines can successfully send and receive messages with MSMQ. MSMQ uses the QMId to know where it should send acknowledgments and replies for incoming messages.Īll the machines must have their own unique QMId. The QMId is stored as a key in the registry, HKEY_LOCAL_MACHINE\ Software\ Microsoft\ MSMQ\ Parameters\ Machine Cache. Worker QMId needs to be uniqueĮvery installation of MSMQ on a Windows machine is represented uniquely by a Queue Manager ID (QMId). This article details common problems encountered with the MSMQ Transport and how to resolve them. This article is part of the NServiceBus Learning Path. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |