Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 9 Jun 2011 15:17:01 +0000 (UTC)
From: "Torsten Mielke (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <2052213199.7206.1307632621367.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (AMQ-3362) Broker does not check for expired
 persistent topic msgs.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Broker does not check for expired persistent topic msgs.
--------------------------------------------------------

                 Key: AMQ-3362
                 URL: https://issues.apache.org/jira/browse/AMQ-3362
             Project: ActiveMQ
          Issue Type: Improvement
          Components: Broker
    Affects Versions: 5.5.0, 5.4.2
            Reporter: Torsten Mielke


When using topics with durable subscriptions, where subscribers disconnect for a while, there is no task that checks for expired messages on the durable subscription.
In case where subscribers are disconnected for hours and message are still sent with a TTL, it may happen that either the producer gets blocked (in case of flow control) or the broker runs out of persistent storage (no flow control) just because of msgs that are already expired.

Similar to queues, there should be a periodic task that checks for expired msgs on durable topic subs. This task should also be configurable using a property similar to [expireMessagesPeriod|http://activemq.apache.org/per-destination-policies.html].

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira