Multiple Windows Services, Multiple Queues with MSMQ and Shared Private Assemblies

[brianbass]

I am having a perplexing issue and am wondering if anyone can see the
flaw in my setup.

I have 3 windows services and 3 message queues. Each service resides
in the same directory and they all have a reference to the same dll(a
private assembly (although it does have a strong key)). The class in
this assembly takes the name of the message queue to monitor in its
constructor. Then the instantiated class constantly reads the queue
(MSMQ transactional message queue) and processes messages and then
commits the transaction.

The desired behavior is that all 3 message queues will get processed
in parallel. But here is what is happening. Queue A will read messages
and process and read messages and process. Eventually all of the
messages in Queue A gets processed. Then Queue B will start to be read
and process only when Queue A is empty. Then Queue C will get
processed only when Queue B is empty.

Very perplexing. I am thinking somehow the shared assembly is loaded
once in memory and each service only gets to use it when the other
service is finished. I would think that the class is instantiated in a
separate memory space and would be independant of the other services
and other queues.

Anyone have any ideas? Thanks,

Brian