May not be “best practice” advice here… but based on real life needs and experience: we have distributed system, 60 boxes running each 10 clients all do task X, and they need to take the next task from a queue. The queue is being fed from one other “client”… We had used inter process communication, … Read more
I had the same error message and the solution was simple. There were a lot of messages sitting on various queues, and the storage limits had been reached. I went to: Server Manager -> Features Right clicked on Message Queuing Selected properties In the General tab un-ticked the storage limits I was informed that services … Read more
You sounds like you’re on the right track. However you could bump up a bit with this: Using SvcConfigEditor.exe Configure WCF Verbose Tracing for Propagate ACtiveity and Activity tracing Configure WCF MessageLogging for “Malformed Messages, Service Messages, Transport Messages” Use LogEntireMessage In End to End, trace it All Make sure you enable these *.config on … Read more
The main functional difference is Service Bus provides out of the box support for message exchange semantics such as topic based routing via publish-subscribe. MSMQ on the other hand is a lightweight store-and-forward queuing system, which supports point-to-point one way messaging. Service Bus: depends on SQL Server, and is a broker. This may be considered … Read more
The official documentation on how to handle Faults is here: Handling Exceptions and Faults Understanding State Changes with the main page being at Channel Model Overview There’s a nice state diagram showing how things happen:
You can read the Performance Counter value for the queue directly from .NET: using System.Diagnostics; // … var queueCounter = new PerformanceCounter( “MSMQ Queue”, “Messages in Queue”, @”machinename\private$\testqueue2″); Console.WriteLine( “Queue contains {0} messages”, queueCounter.NextValue().ToString());
If you are using Visual Studio – Open Server Explorer under Servers/[Server Name] there is Message Queues folder that gives you view as well.
I ran into the same issue trying to write to the MSMQ through ASP.NET (Windows 7). I added “Receive Message” “Peek Message” and “Send Message” permissions and it works correctly now. If you’re running this through ASP.NET, then you’re probably under the IIS_IUSRS account.
With all due respect to @Juan’s answer, both are ways of exchanging data between two disconnected processes, i.e. interprocess communication channels (IPC). Message queues are asynchronous, while webservices are synchronous. They use different protocols and back-end services to do this so they are completely different in implementation, but similar in purpose. You would want to … Read more
I wrote a blog post a while back comparing MSMQ and RabbitMQ (among others): http://mikehadlow.blogspot.co.uk/2011/04/message-queue-shootout.html RabbitMQ gave slightly better performance than MSMQ, but both were comprehensively out performed by ZeroMQ. If performance is your main criteria, you should definitely look at ZeroMQ. It’s worth noting that RabbitMQ and MSMQ are very different beasts. MSMQ is … Read more