[
https://issues.apache.org/jira/browse/AMQ-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac resolved AMQ-3362.
--------------------------------
Resolution: Fixed
Fix Version/s: 5.6.0
Assignee: Dejan Bosanac
Fixed with svn revision 1135649
> 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.4.2, 5.5.0
> Reporter: Torsten Mielke
> Assignee: Dejan Bosanac
> Fix For: 5.6.0
>
>
> 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
