-
Bug
-
Resolution: Done
-
Major
-
AMQ 7.2.4.GA
-
3
-
Release Notes
-
-
Documented as Resolved Issue
-
ARTEMIS-1011
-
Verified in a release
-
AMQ Broker 2019, AMQ Broker 2319
There is still a problem how producer msg/s rate is calculated in QueueImpl.getRate() for slow consumer detection. It calculates only messages added during the last slow consumer check period. As this is used to figure out, in which msg/s rate the queue could serve the consumer then it should also take into account messages which are already in queue at the start of queueRateCheckTime period.
Current implementation is problem for cases when messages are sent to queue in bursts, for example producer sends 1000s messages in a few seconds and then stops and will do that again in 1 hour. QueueImpl.getRate() method returns 0 msg/s for slow consumer check period set to for example 5 min and slow consumer detection will be skipped.
- clones
-
JBEAP-9331 Slow consumers not disconnected if producer msg/s rate is low
- Closed
- relates to
-
JBEAP-8708 Consumers killed as slow even if overall consuming rate is above threshold
- Closed
-
ARTEMIS-1011 Loading...