I'm looking to use MSMQ to improve the performance of my Web Service. I would like the web service to drop something onto the queue, and then a windows service (sitting on another server) to come along and pick up that object - but only remove it once it's been processed and placed in the database - I don't however want another windows service to come and pick up the same item (because it's first in the queue) and process it aswell...does that make sense

If someone could point me in the direction of a great article about this I would be most grateful.

I'm also looking for things about clustering the webservice - so I assume the msmq would then be split across a number of servers - to me that sounds a bit dodgey - is it Would I need to have a server dedicated to msmq so that the 10 (for example) web services could place things on the queue, and then the 10 windows services can come along and pick the information up Is that possible

Thanks!! Paul
(first post! woo!)

Re: ASMX Web Services and XML Serialization .NET and MSMQ

Pablo Cibraro

Hi Paul,

In order to make the things easier for you, you have two options here, WCF ( or a MSMQ custom transport for WSE (

Both options meet your requeriments, altough the first one is more official. You can also use transactional queues, so if an error happens in the service, the message is returned to the queue.



Re: ASMX Web Services and XML Serialization .NET and MSMQ


Thank u Pablo. good article to newbie like me. thanks again.