Hi gang,
I'm seeing some baffling behavior w.r.t. the concurrent consumption of messages, and I'm hoping someone can jump in and say "that's because you need to tweak the wiggle-wobble setting". Here's some context:
* 8 core CPU
* Windows 7 Ultimate
* MassTransit 2.7.x (I haven't rolled back yet to see if it's happening with 2.1.x)
* RabbitMQ
We just noticed that there seems to be a hard limit of 10 concurrent messages consumed in our processes, eventhough we've been setting the limit to 100, 1000, etc.. If I change the call to SetConcurrentConsumerLimit to 2, this is honored... but anything above 10 is capped to just 10.
I thought something might be messing with the .Net thread pool limits, so I queried ThreadPool and dumped these stats within my consumer and find:
Current workerThreads [32767], complPortThreads [1000]
MAX workerThreads [32767], complPortThreads [1000]
MIN workerThreads [8], complPortThreads [8]
So I know the default .Net thread pool is not forcing this limit.
In the past (and unfortunately I don't remember the timing and/or version of MassTransit we were using them), I've seen 100's and 1000's of concurrent messages going through my consumers... but now it's just 10.
Any ideas what might be happening? is there a newish config setting that I need to set in addition to the ConcurrentConsumerLimit? anything system-wide that could be limiting MassTransit when trying to pull from Rabbit? etc..
The few remaining hairs on my head thank yas in advance for any help,
Tyler