-
Bug
-
Resolution: Done
-
Major
-
JBoss A-MQ 6.0
-
None
Using AbortSlowAckConsumerStrategy with abortConnection=false; sometimes consumers are not aborted. This results in messages being trapped in the consumers prefetch and not being released to be consumed by other consumers
At the moment the broker asked the client side consumer to stop - a graceful abort consumer.
It would be good to have a forceful shutdown of consumers on the broker side in cases where the client side consumer is not responding, hung etc.
- blocks
-
ENTMQ-574 introduce logic into the failover transport not to recreate "aborted" slow consumers.
- Closed