activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-3507) Large number of expiring messages causing QueueSize to grow.
Date Wed, 21 Sep 2011 12:15:09 GMT

     [ https://issues.apache.org/jira/browse/AMQ-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gary Tully resolved AMQ-3507.
-----------------------------

    Resolution: Fixed

fix in http://svn.apache.org/viewvc?rev=1173583&view=rev

the file pending message cursor now delegated to the destination to process an expired message.
Single code path for all expiry.

> Large number of expiring messages causing QueueSize to grow.
> ------------------------------------------------------------
>
>                 Key: AMQ-3507
>                 URL: https://issues.apache.org/jira/browse/AMQ-3507
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.2, 5.5.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: activemq, expiry, fileCursor, nonPersistent
>             Fix For: 5.6.0
>
>
> Issue with file pending message cursor (non persistent messages) discarding expired messages.
It currently bypasses the destination expiry logic and leaves messages in the store.
> In the main, an expired messages don't get added to the cursor or are pruned by the async
expiry processing task, but when memory limits are exceeded this problem can occur.

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

        

Mime
View raw message