I've submitted https://issues.apache.org/jira/browse/AMQ-5362 to capture
this issue, and https://issues.apache.org/jira/browse/AMQ-5361 to capture
the ability to use more than one slow consumer strategy at the same time
(since it's unlikely that anyone would want to identify slow consumers
based so
We're sending non-persistent messages to a topic where some consumers may
sometimes be slow. We've configured a slowConsumerStrategy of
AbortSlowConsumerStrategy to disconnect any consumers that happen to be
slow. The detection of a slow consumer relies on there being at least 2x
the consumer's p
