Why does one misbehaving Notification service consumer stop events to other consumers of the same channel?
The channel’s global queue was filled by the bad consumer. When the MaxQueueLength admin property is set on a channel without setting MaxEventsPerConsumer QoS property or setting MaxEventsPerConsumer >= MaxQueueLength then a single slow/misbehaving consumer’s queue can fill up the entire channel’s queue. The full channel queue results in no events getting queued for some or all of the remaining consumers. The events that are not enqueued can result in a memory leak. When setting the MaxQueueLength admin property, set the MaxEventsPerConsumer QoS property to a value less than the MaxQueueLength.
Related Questions
- I received a Notification for Jury Service, Qualifying Questionnaire and Voir Dire Questionnaire, and I am requesting to be excused. Do I still need to complete the juror questionnaire?
- Why does one misbehaving Notification service consumer stop events to other consumers of the same channel?
- When can consumers begin to use their opt-out rights for credit card changes?
