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] Updated: (AMQ-2468) Calling purge on a large queue causes OutOfMemoryError in the broker.
Date Wed, 28 Oct 2009 15:30:53 GMT

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

Gary Tully updated AMQ-2468:
----------------------------

    Summary: Calling purge on a large queue causes OutOfMemoryError in the broker.  (was:
OOM when using JMX purge on a Queue with lots of messages in it)

> Calling purge on a large queue causes OutOfMemoryError in the broker.
> ---------------------------------------------------------------------
>
>                 Key: AMQ-2468
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2468
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.3.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.4.0
>
>
> the problem is worse when there is a slow consumer and steady producer in the mix.
> Problem is that purge forces a page in and a dispatch but the dispatch ends up appending
to pagedInPending which is not limited and not bound by the usage metrics so it only appears
as an OOM.
> Fixing purge to not dispatch helps but the presence of a consumer incurs a dispatch on
message sending so over time a steady producer will give the same behavior.
> Purge is a special case that highlights the problem of no restriction on pagedInPending
with a very slow consumer. If consumers can keep up, or if producer flow control is used,
or lazyDispatch, this issue can be avoided.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message