#msmq

Read the full report on -

Configuring WCF Service with MSMQ protocol on IIS – Invalid URI: The hostname could not be parsed

I am trying to set up a WCF service on IIS ( IIS7, Windows 7 ) using configured endpoints and, as is typical with IIS configuration, it is a world of hurt. The service works fine working under the debugger on VS2010, but when I come to deploy it I get the following message upon opening http://localhost:9000/MyApplication/_vti_bin/ListData.svc :

[UriFormatException: Invalid URI: The hostname…

I have been working on few things recently and wanted to automate message queuing. Three golden steps need to be followed before start running this scripts.

Set the execution policy to unrestricted

Make sure the user have got administration access on the server

Enable MSMQ features in the windows server.

Now you are all set

This script is available under https://github.com/mani0070/AzureAutomatio…

Fixed: MSMQ very slow to receive messages #fix #development #computers

MSMQ very slow to receive messages

We’ve got a pretty large MSMQ environment setup which today decided to grind to a halt.

(Everything is a VM under vSphere 4.0 Update 1)

There are 8 Web Servers which receive data from clients on the net. These machines all have MSMQ installed and simply send the MSMQ message to the main MSMQ server. Messages are currently piled up in the outbound queue. These…

Solution: nServiceBus vs Mass Transit vs Rhino Service Bus vs other? #dev #solution #development

nServiceBus vs Mass Transit vs Rhino Service Bus vs other?

Just doing some quick spikes into possibly using a messaging system to process files that are in a nicely decoupled work flow system.

What are the pro’s and cons that people have found of using each of the above frameworks? What are the advantages of using these versus a hand-rolled MSMQ system with the WCF bindings and/or non-MSMQ…

This is what wiki is saying wiki

MSMQ is essentially a messaging protocol that allows applications running on separate servers/processes to communicate in a fail-safe manner. A queue is a temporary storage location from which messages can be sent and received reliably, as and when conditions permit. This enables communication across heterogeneous networks and between computers which may not always be connected. By contrast, sockets and other network protocols assume that direct connections always exist.

.net has System.Messaging which gives us access to Msmq API. As a developer you have 2 ways to make your application to use messaging infrastructure.

Pooling consumer

As the name is mentioning the application will use a message adapter in an infinite loop to pool the message queue for messages. When there is a message it will be dequeued and processed.

public class PoolingConsumer : IDisposable { readonly MessageQueue _channel; public PoolingConsumer(string queueName) { _channel = new MessageQueue(queueName); } public Message Receive() { return _channel.Receive(); } public void Dispose() { _channel.Dispose(); } }

Event-Driven consumer

When you want to process a message as soon as it arrives asynchronously then go event driven. This is the fastest way when you don't need transactions. Is better suited for monitoring, notifications.

public class EventDrivenConsumer : IDisposable { readonly MessageQueue _channel; public EventDrivenConsumer(string queueName) { _channel = new MessageQueue(queueName); } public void RegisterHandler(Action<Message> handler) { _channel.ReceiveCompleted += (sender, args) => { var queue = sender as MessageQueue; handler(queue.EndReceive(args.AsyncResult)); queue.BeginReceive(); }; _channel.BeginReceive(); } public void Dispose() { _channel.Dispose(); } }

Usage sample

[Test] public void ReceiveShouldPullAMessageFromTheQueue() { const string receiver = @".\Private$\receiver"; new MessageQueue(receiver).Send(new Message()); var message = new PoolingConsumer(receiver).Receive(); Assert.IsNotNull(message); } [Test] public void HandleGetsCalledWhenAMessageIsAvailableInTheQueue() { const string receiver = @".\Private$\eventingendpoint"; Message output = null; var endpoint = new EventDrivenConsumer(receiver); endpoint.RegisterHandler(msg => { output = msg; }); new MessageQueue(receiver).Send(new Message()); Thread.Sleep(10); Assert.IsNotNull(output); }

Conclusion

So, my messages weren't being deleted in my MSMQ even though I had set the timeout value in Biztalk to have it delete after 1 minute! What's going on?

I am currently developing an application where Biztalk writes messages to a private MSMQ queue. One thing I have realized is that the Timeout value on the send port is not necessarily the time-to-live for the message once it gets into the MSMQ, but simply the time it takes for the message to hit the MSMQ queue. 

I ended up writing a small windows service that ended up being really simple to purge all messages in my queue. 

string[] __privatequeues = ConfigurationManager.AppSettings["PrivateQueues"].Split(','); foreach(string __queueName in __privatequeues) {      string __queuepath = String.Format(".\\private$\\{0}", __queueName);      if (MessageQueue.Exists(__queuepath))      {           using (MessageQueue __queue = new MessageQueue(__queuepath))           {                __queue.Purge();           }      } }

I need to figure out how to get syntax highlighting working properly, but I'll do that when I have a bit more time.

Anyways, that code above simply loops through all of the comma delimited queues I have located in my app.config file and purges all messages in each of those queues. I ran this as a scheduled task and now it runs great! 

So afterwards, I went into MSMQ and looked at the column Message Quote Size. I was wondering why that kept growing even though my messages were getting purged every so often. Turns out that the MSMQ Message Quota Size refers simply to the amount of bytes in the message payload for all the messages. So nothing really to worry about. If you have one message, it will show you the amount of bytes that one message takes up.