Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Tue, 6 Oct 2015 10:16:27 +0000 (UTC)
From: "M Rahimi (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.12902658.1444126576000.34885.1444126587157@Atlassian.JIRA>
In-Reply-To: <JIRA.12902658.1444126576000@Atlassian.JIRA>
References: <JIRA.12902658.1444126576000@Atlassian.JIRA>
 <JIRA.12902658.1444126576992@arcas>
Subject: [jira] [Created] (AMQ-6000) Pause/resume feature of ActiveMQ not
 resuming properly
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

M Rahimi created AMQ-6000:
-----------------------------

             Summary: 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
             Fix For: 5.12.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)