activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6000) Pause/resume feature of ActiveMQ not resuming properly
Date Tue, 06 Oct 2015 11:16:26 GMT

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

Gary Tully commented on AMQ-6000:
---------------------------------

To sort this, I think there should be a call to wakeup() in org.apache.activemq.broker.region.Queue#resumeDispatch

> Pause/resume feature of ActiveMQ not resuming properly
> ------------------------------------------------------
>
>                 Key: AMQ-6000
>                 URL: https://issues.apache.org/jira/browse/AMQ-6000
>             Project: ActiveMQ
>          Issue Type: Sub-task
>          Components: Broker, JMX
>    Affects Versions: 5.12.0
>            Reporter: M Rahimi
>              Labels: features
>
> The problem is that, when you *resume* the message delivery,
> # If there is a message entering the queue: the broker will immediately send the pending
messages to the consumer which is totally OK.
> # But if no message _enters_ the queue: the pending messages in the queue will not be
sent to the consumers until the expiration checking is performed on the queue (which by default
is 30 seconds and can be controlled by the _expireMessagesPeriod_ attribute) and non-expired
messages will be sent to the consumers afterwards.
> Obviously we can change the _expireMessagesPeriod_ to limit this delay, but when you
need a milisec precision, performing the expiration check every milisec will not make sense.
> How is it possible to force the queue to start sending messages immediately after resumption?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message