activemq-issues mailing list archives

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

    [ https://issues.apache.org/jira/browse/ARTEMIS-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15885812#comment-15885812
] 

Jiri Danek commented on ARTEMIS-1001:
-------------------------------------

bq. Documentation says that it should be in minutes.

Where, exactly?

> 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