activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Miroslav Novak (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ARTEMIS-1001) slow-consumer-check-period is in minutes but behaves like with seconds
Date Mon, 27 Feb 2017 11:55:45 GMT
Miroslav Novak created ARTEMIS-1001:
---------------------------------------

             Summary: slow-consumer-check-period is in minutes but behaves like with seconds
                 Key: ARTEMIS-1001
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1001
             Project: ActiveMQ Artemis
          Issue Type: Bug
          Components: Broker
    Affects Versions: 1.5.3
            Reporter: Miroslav Novak


Attribute {{slow-consumer-check-period}} is in minutes but {{SlowConsumerReaperRunnable} thread
is scheduled as it's configured with seconds.

Problem is in {{QueueImpl.scheduleSlowConsumerReaper}} method:
{code}
slowConsumerReaperFuture = scheduledExecutor.scheduleWithFixedDelay(slowConsumerReaperRunnable,
settings.getSlowConsumerCheckPeriod(), settings.getSlowConsumerCheckPeriod(), TimeUnit.SECONDS);
{code}

contains {{TimeUnit.SECONDS}} instead of {{TimeUnit.MINUTES}}. 

I tried to debug it and can see that {{settings.getSlowConsumerCheckPeriod()}} returns 1 which
is in minutes. This seems to be easy fix.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message