MSMQ 4.0 - what's new in Computer Management? - MSMQ from the plumber's mate. I'm now the proud owner of a working Windows Server 2008 installation (I know, I know, I should have got into the beta but I've been busy..) so I thought I'd have a quick look at what's different in Computer Management.
You'll be happy to know that little has been changed within MSMQ management except that there are now two places to do the same tasks (Computer Management and Server Manager). MSMQ is now a "feature" of the operating system so is found under Features in Server Manager: Getting MSMQ messages out of Windows Server 2008 remotely - MSMQ from the plumber's mate. I'm now into full swing looking at MSMQ 4.0 on Windows Server 2008 using Virtual Server.
I haven't got round to installing 2008 on my 64-bit laptop and desktop yet but maybe in the summer sometime when customers are on vacation I'll have the time. Sending messages works fine but receiving them fails (0xC00E0069 Remote Machine Not Available). Clear the way - MSMQ coming through - MSMQ from the plumber's mate. [[Edited Ping information - 20th May 2008]] A reasonably common question is "what ports does MSMQ use?
" Usually the infrastructure guys have their routers locked down tight and want to open up only the bare minimum to let your new MSMQ application through. The problem can be in understanding what the different ports that MSMQ uses are actually for. First, MSMQ operates in two distinct ways to move data: Pushing messagesPulling messages. Reading Messages from Remote Queues. Although remote read operations are not part of the optimal messaging model, reading messages from remote nontransactional queues is fully supported.
Remote reading is typically used to distribute the work load among servers. Remote reading is a high-overhead and therefore inefficient process. Including remote read operations in an application limits scaling. Message Queuing supports sending transactional messages to remote queues, but does not support reading messages from a remote queue within a transaction. Transactional MSMQ. Couple of weeks ago I have discovered excellent support from Microsoft that allows one to easily solve the producer-consumer problem.
As stated on Wikipedia, the producer-consumer problem (also known as the bounded-buffer problem) is a classic example of a multi-process synchronization problem. The problem describes two processes, the producer and the consumer, who share a common, fixed-size buffer used as a queue (link). Working with MSMQ Triggers. Introduction In a world of enterprise applications built on Microsoft technology, MSMQ has been the solution for effective messaging.
MSMQ has been one of the most powerful methods for distributed applications to talk with each other in a connectionless and asynchronous manner. But using MSMQ may require a lot of infrastructure code to be written around it. For instance, you may have a sending application sending messages to a queue and a listening application constantly listening on the queue to pick them up as and when they arrive. The listening application must be up and running, constantly waiting for messages to appear on the queue.
Working with MSMQ Triggers. Programming MSMQ in .NET - Part 2: Transactional Messaging. Introduction In the previous article, we saw some very basics of MSMQ programming like creating a queue, sending and receiving simple messages etc.
In this article, we shall consider an important aspect of programming MSMQ: Transactional messaging. We shall start off by understanding why you need transactional messaging, what it is, followed by some simple code snippets showing how it can be done in .NET. Finally, we shall wrap up the article considering two case studies where transactional messaging with MSMQ has been applied. Nine Tips to Enterprise-proof MSMQ. Ince the release of the first version of MSMQ in December of 1997, it has provided the plumbing required by many enterprise applications.
Before MSMQ, developers implemented tools with similar functionality using input/output directories with files, SQL Server tables, DCOM, TCP/IP sockets, etc. The major shortcoming in all these approaches was the complexity of delivering a robust system—performance took a back seat. MSMQ's release provided the standardized messaging platform that many projects needed—a great head-start for developers building enterprise solutions. Unfortunately, MSMQ fell short in delivering the level of performance and robustness required by many projects.
Yoel's Microsoft Message Queue (MSMQ) space. One of the missing pieces that we always planned to add to MSMQ and never had time to is WMI provider.
In a way, the MSMQ performance counters already expose a way to query the MSMQ status through WMI. For example, the following query will find queues with more than 100 messages: Dim LocatorSet Locator = CreateObject("WbemScripting.SWbemLocator")Dim objsSet Service = Locator.ConnectServer(" What publically available tools are there for troubleshooting MSMQ problems? - MSMQ from the plumber's mate. Here's a list of utilities that you may want to familiarise yourself with before trying to resolve any MSMQ networking issues you encounter.
Most of them are already well documented on TechNet so there isn't much for me to say except "I wish there were more! " MSMQ Backup The most important tool is MQBKUP.EXE so that if you can roll back any changes you make. This command-line utility (which comes with MSMQ) can backup and restore message storage files, log files, transaction log files, and registry settings. A full description is available in the following TechNet article: Backing up and restoring messages. Interrogating Systems with WMI. Ever wondered how to create a Winmsd type program to interrogate yours or other systems on the network? Microsoft has the answer with a technology called WMI or Windows Management Instrumentation. (WMI is the Microsoft implementation of Web-Based Enterprise Management (WBEM), which is an industry initiative to develop a standard technology for accessing management information in an enterprise environment.
MSMQ QXplorer / Code / [r3] /QXplorer 2.0. MSMQ Managment Console - Documentation. Most of information available here also available in the tool itself (type '? ' when in command mode) although it is a little less readable. Notes. Emil's Lost & Found Archive » Retrieving the message count for MSMQ queues.
Home > .Net programming, PowerShell, Windows tips > Retrieving the message count for MSMQ queues Sometimes it can be useful to retrieve the number of messages in an MSMQ queue, for example for monitoring. However, it’s not immediately apparent how to do it if you google it, so here are my thoughts on the subject. Other blog posts suggest iterating over messages (e.g. Counting Messages in an MSMQ MessageQueue from C#) or doing it using WMI. WMI is the best alternative in my opinion and if you want a quick way of doing it then PowerShell is the easiest:
Be Prepared: Known Issues for Upgrading to Windows Server 2008 - Motley Queüe. There are a few differences in MSMQ and IIS functionality between Windows Server 2003 (MSMQ v3.0) and Windows Server 2008 (MSMQ v4.0). This means that there are a few configuration changes you may have to make to your MSMQ system post-upgrade to make everything function the way it did on Windows Server 2003.
Issues with HTTP and transactional messages: MSMQ’s transactional message support uses internal messages called “order ACKs” to coordinate between sender and receiver so that no user messages are lost. When transactional messages are sent via HTTP, the URLs used to send the order ACKs back to the sender sometimes contain the special character “+”.
ActiveXperts Network Monitor. ActiveXperts Software B.V. contact@activexperts.com Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise noted. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of ActiveXperts Software B.V. Products named herein may be trademarks of their respective manufacturers and are hereby recognized. Counting Messages in an MSMQ MessageQueue from C# Jondot/qtools. [MSMQ]Shell for basic opeartions with MSMQ ? MSMQ in WCF. Posting Message to MSMQ from SQL Server.