Queue names for WAS hosted WCF service

On WCF forums, I have noticed a common issue that developers face when hosting their WCF service in WAS. The issue is that the service does not get activated. Often, the reason is that the queue name does not match the service endpoint name. This msdn article talks about this behavior. In a nutshell “It’s…

0

Performance optimization when using MSMQ with WCF

There are a number of factors that can affect the performance of your enterprise application that uses MSMQ with WCF. Nicholas Allen discusses some of these design decisions in his Optimizing MSMQ article. Another good reference is Best Practices for Queued Communication. This article also talks about how you can use WCF and MSMQ to…

0

Checklist for using MsmqIntegrationBinding

The MsmqIntegrationBinding allows users to create WCF applications that send and receive messages to and from existing MSMQ applications that use System.Messaging or other MSMQ APIs. The operation contract should be one-way i.e. IsOneWay = true. Action property should be specified in the operation contract to indicate a service operation handles all messages that the service…

0

A double negative System.Messaging exception

        Message message = new Message();        message.CorrelationId = Guid.NewGuid().ToString(); The above code snippet compiles but when you execute it, you get a System.InvalidOperationException with an ambiguous message:“Identifier is not in the incorrect format.” There is a typo in the exception above and it should actually say:“Identifier is not in the CORRECT format.” The InvalidOperationException is thrown…

1

Dealing with PRIVATE= formatnames

If your MSMQ environment has AD Integration installed, you can use PUBLIC= formatnames for public queues and PRIVATE= formatnames for private queues. PUBLIC= formatnames are pretty easy to work with: if you know the path of the queue, you can get or construct a PUBLIC= formatname, and if you have a PUBLIC= formatname, you can…

0

Configuring a Remote WAS-hosted Queue

Creating a reliable service for MSMQ has been made simpler with the introduction of Windows Process Activation Service (WAS). Your deployment scenario may make it easier to have WAS running on a separate machine from where the MSMQ queue of interest is located. This post will go through the steps to get a simple sample…

0

Queue Matching Behavior in WAS

With the release of Windows Vista (and subsequently Windows Server 2008), a new way to host WCF services was introduced: Windows Process Application Service (WAS). Services that use MSMQ now have the option of being hosted in WAS. One of the most frequently asked questions relates to matching the service file (*.svc file) with the…

0

WAS hosting on Windows 7

IIS 7 allows isolation of web application pools from each other by providing the ability to run application pools as separate identities. The identity of an application pool is the name of the service account under which the application pool’s worker process runs. Running an application pool under an account that has high-level user rights…

0