[
https://issues.apache.org/jira/browse/AMQ-5157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17244619#comment-17244619
]
Matt Pavlovich commented on AMQ-5157:
-------------------------------------
Additional destinationPolicy setting for topics has been added:
expireMessagesPeriod
See: [Destination Policies|https://activemq.apache.org/per-destination-policies]
This ticket is scheduled to close in 30 days if there are no further updates.
> Non persistent Messages not getting expired
> -------------------------------------------
>
> Key: AMQ-5157
> URL: https://issues.apache.org/jira/browse/AMQ-5157
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.8.0
> Reporter: Anuj Khandelwal
> Priority: Major
>
> It is coming from
> http://activemq.2283324.n4.nabble.com/Non-persistent-Messages-Not-getting-expired-even-after-expiration-time-exceeded-td4680428.html#a4680459
>
> Problem: Non-persistent messages, if off lined to tmp storage (may be because
> of inactive durable subscriber), won’t be expired until they are scheduled
> for dispatch.
> Test scenario: Non persistent message is sent from the producer to the topic
> which has inactive durable subscriber, this message will be stored in
> non-persistent message tmp store "activemq-data/broker/tmpstorage/".
> This message is not getting deleted even after Expiration time is exceeded.
> According to discussion on ActiveMQ user forum, it will only be expired when
> the message is ready to dispatch. Which should not happen.
> Ideally broker should expire the message if expiration time exceeds
> irrespective of message is ready to dispatch or other things.
> Thanks,
> Anuj
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
