No slow consumer strategy is enabled by default, so if you haven't configured anything, then the answer is "never."
If you choose to use the strategy you referenced, configuration details (including defaults) are at https://dzone.com/articles/coming-activemq-59-new-way. Or you can use the original strategy (SlowConsumerAbortStrategy) if you're more concerned with consumers being slower than producers overall than with a single message taking a long time for a given consumer. Delivery of a non-acknowledged message to a new consumer does indeed count as redelivery. Tim On Aug 25, 2017 10:02 AM, "Raffi" <raffi.onj...@gmail.com> wrote: > ActiveMQ 5.12 > > When messages are dispatched to a consumer, how long will the broker wait > before it considers the consumer "slow" assuming the consumer does not ack > the message and the connection remains active? We're not using any slow > consumer strategy in the broker, so when I found this I wasn't sure it was > enabled by default: > > http://activemq.apache.org/maven/5.9.0/apidocs/org/ > apache/activemq/broker/region/policy/AbortSlowAckConsumerStrategy.html > > Another question: If a message is dispatched to a different consumer, is > that considered "redelivery" if the initial consumer never acked or raised > an exception while processing the message? > > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/Slow-consumer-acknowledgment-timeout-tp4730007.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
