Net.Msmq Binding Not Picking Up Messages in Queue as soon as the application pool gets recycled

Question

Hi,
We are trying to implement a wcf service that exposes a net.msmq endpoint.  We are running windows server 2008 R2/IIS 7.5 running on a DOMAIN mode.
1. Our service is called service.svc and it is deployed under an application called Test in the default website (application pool running under network service)
2. The url to reach the service webpage is http://machinename/Test/service.svc.
3. We created a private queue called Test/service.svc and we configured permissions for network service to full control.
Now, when the application pool is "alive" the service picks up the messages correctly, but as soon as the application pool gets recycled (because of timeout or any other reason), the service stops picking up the messages, that just sit in the queue until the service starts again by browsing to the service webpage (http://machinename/Test/service.svc)
I know this is a popular question, but I already tried several solutions with no luck (for example, we triedhttp://keithelder.net/blog/archive/2009/06/03/fix-for-wcf-netmsmqbinding-not-picking-up-messages-in-queue.aspx,http://www.codewrecks.com/blog/index.php/2009/03/17/hosting-a-wcf-service-based-on-msmq-in-iis7/,http://social.msdn.microsoft.com/Forums/en-US/wcf/thread/a1df55c4-e642-442a-9057-f0aec278d10c/ and other ones)
Any Help?
If this post is helpful, please mark it as such
Alessandro Cardoso
MVP | Microsoft Heroes | MCT
blog: http://itaustralia.spaces.live.com
http://cardosoalessandro.spaces.live.com

Answer 1

Hi Steven,
I am Alessandro's colleague, I am working with him on these net.msmq issues. 
Our configuration includes a transactional queue called Test/Service.svc (unauthenticated,
we shut down all security for the moment...does it matter?) and these attributes on the service:
[ServiceContract]
public interface IService
[OperationContract(IsOneWay=true)]
void ProcessMyMessage(MyClass parameter);
[ServiceBehavior(InstanceContextMode = InstanceContextMode.PerCall, TransactionIsolationLevel = IsolationLevel.Serializable, TransactionTimeout = "00:03:00")]
public class Service: IService
[OperationBehavior(TransactionScopeRequired = true, TransactionAutoComplete = true)]
public void ProcessMyMessage(MyClass parameter)
//Do some stuff here
The service is hosted on IIS 7.5 under an application called Test (so that the full http address of the service is http://machine/Test/Service.svc).
In the configuration (for both client and service) we specified None for the security mode, "true" value in durable and exactlyOnce
The Net.msmq Listener Adapter windows service is running fine under the Network Service account (the same as our application pool)
Is there something we are missing?
Also, can you explain how a transaction not configured properly can create this behaviour? In my understanding the process of delivering a message happens in 3 steps (I remember a nice picture of this the Juval Lowy book):
1) Transaction 1: client delivers message to local instance of msmq. The transaction rolls back if the message does not get delivered.
2) Transaction 2: the local instance of msmq delivers the message to the remote (service) instance of msmq. The transaction rolls back if the message does not get delivered.
3) Transaction 3: wcf activates my service which picks up the message and process it. The transaction rolls back if the service fails to pick up the message or does not complete the transaction (for example, because of an unhandled exception).
The message gets delivered to the service machine successfully, so I am assuming that steps 1 and 2 are executed correctly. If my service was not configured to handle transaction properly, wcf should still activate it and do something with it. Or at least,
if it doesn't get activated at all, this should be the case even when the application pool is well alive and awake, because it should be a configuration problem. Instead, the service works great if the appPool is alive and it never gets activated when the
appPool is sleeping (absolute nothing in the .svclog trace file generated by the service). Am I saying something wrong?