You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2017/02/27 15:11:45 UTC
[jira] [Closed] (ARTEMIS-1001) slow-consumer-check-period is in
minutes but behaves like with seconds
[ https://issues.apache.org/jira/browse/ARTEMIS-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram closed ARTEMIS-1001.
-----------------------------------
Resolution: Not A Problem
> 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)