[
https://issues.apache.org/activemq/browse/AMQ-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-2481.
-----------------------------
Resolution: Fixed
Fix Version/s: 5.4.0
fix in r834543
> OOM due to message expiry processing with large numbers of messages in queue
> because of slow or absent consumers.
> -----------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-2481
> URL: https://issues.apache.org/activemq/browse/AMQ-2481
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.3.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.4.0
>
>
> when a large of messages in queue,and no consumer or the consumer is very
> slow, the OOM problem occur, because :
> in org.apache.activemq.broker.region.Queue,the 588 line is :
> doBrowse(true, browsedMessages, this.getMaxExpirePageSize());
> ,transform to :
> doBrowse(false, browsedMessages, this.getMaxExpirePageSize());
> is ok.
> from user list:
> http://old.nabble.com/Out-of-Memory-on-5.3-ts26064098.html#a26264779
> Problem is messages get paged into memory with out any limiter.
> *Note:*
> disabling periodic expiry processing using a destination policy can work
> around this. set expireMessagesPeriod = 0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
