Simon Lundstrom created AMQ-7079:
------------------------------------

             Summary: Using abortSlowAckConsumerStrategy aborts slow consumer 
even though it has disconnected
                 Key: AMQ-7079
                 URL: https://issues.apache.org/jira/browse/AMQ-7079
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
            Reporter: Simon Lundstrom


When testing AMQ-7077 I noticed that if an consumer gets tagged as slowConsumer 
and then the consumer disconnects ActiveMQ will abort the slow consumer (even 
though it already has disconnected).
  
 Somewhere in between of 13:09:10 and 13:09:42 the consumer disconnects.
{code:java}
2018-10-18 13:09:10,735 | INFO  | sub: 
ID:kaka.it.su.se-51120-1539860894594-1:1:1:1 is no longer slow | 
org.apache.activemq.broker.region.policy.AbortSlowAckConsumerStrategy | 
ActiveMQ Broker[localhost] Scheduler
2018-10-18 13:09:42,836 | INFO  | aborting slow consumer: 
ID:kaka.it.su.se-51120-1539860894594-1:1:1:1 for 
destination:queue://su.it.linfra.simlu | 
org.apache.activemq.broker.region.policy.AbortSlowConsumerStrategy | ActiveMQ 
Broker[localh
{code}
Configuration:
{code:xml}
[…]
                <policyEntry queue="su.it.linfra.simlu">
                  <slowConsumerStrategy>
                    <abortSlowAckConsumerStrategy checkPeriod="1000" 
maxTimeSinceLastAck="3000" />
                  </slowConsumerStrategy>
                </policyEntry>
[…]
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to