[
https://issues.apache.org/jira/browse/AMQ-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-6000.
-------------------------------
Resolution: Fixed
Assignee: Timothy Bish
Fix Version/s: 5.13.0
> Pause/resume feature of ActiveMQ not resuming properly
> ------------------------------------------------------
>
> Key: AMQ-6000
> URL: https://issues.apache.org/jira/browse/AMQ-6000
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMX
> Affects Versions: 5.12.0
> Reporter: M Rahimi
> Assignee: Timothy Bish
> Labels: features
> Fix For: 5.13.0
>
>
> 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)
