Geeks With Blogs
MSMQ from the plumber's mate MSMQ is part of your business' IT plumbing which makes you the plumber and I'm your mate. February 2011 Entries
Ever helpful Windows…
I’m doing some troubleshooting for a relative and asked them to send me a zipped copy of their registry which they dutifully did. When I tried to extract the registry file, though, Windows jumped in the way and said “No”. This made sense as registry files are dangerous things in the hands of the ignorant. So I clicked the link to see if it would tell me how to get at the reg file but found the result less than helpful. So off to the Internet and found an excellent answer on how to get round this: ......

Posted On Saturday, February 19, 2011 3:01 PM

Need suggestions on what you regard as “security”
I’m currently writing a large piece on MSMQ security and wanted to check I was covering the right areas. I have some doubts as I’ve seen the occasional MSMQ forum question where a poster has used the word “security” in different contexts to what I was expecting. So here are the areas I plan to cover: Message security encryption on the wire (SSL and IPSEC) encryption of the message (MSMQ encryption) encryption of the payload (data encryption) signing and authentication Queue security SIDs and ACLs ......

Posted On Friday, February 11, 2011 8:48 PM

Service pack 1 on the way for Windows 7 and Windows Server 2008 R2
On the MSMQ front, only two hotfixes are listed: 2028997 - FIX: Message Queuing may become unresponsive in Windows 7 or in Windows Server 2008 R2 974813 - FIX: You cannot send or receive messages by using Message Queuing 4.0 or Message Queuing 5.0 after you configure the BindInterfaceIP registry entry. from a total of 625 documented for the service pack. There may, of course, be undocumented changes where an update was not previously released separately and so has no associated KB article published. ......

Posted On Friday, February 11, 2011 3:37 AM

“Why do transactional messages all have the same priority?”
I answered this question on the MSMQ forum on MSDN and thought it worth sharing here. The poster wanted to know why all transactional messages have a fixed priority of zero (instead of 0 through 7). They wanted the guaranteed delivery of messages to a queue but wanted to assign different levels of priority. Some aspects of MSMQ were defined way back in the last century and this is one of them. If I remember right, the reason was to avoid the following scenario: You have a single transaction of 3 ......

Posted On Thursday, February 3, 2011 2:20 AM

Copyright © John Breakwell | Powered by: GeeksWithBlogs.net | Join free