You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2009/05/22 12:41:50 UTC
[jira] Created: (AMQ-2265) potential OOM (OutOfMemory) on consumer
when all prefetched messages expire
potential OOM (OutOfMemory) on consumer when all prefetched messages expire
---------------------------------------------------------------------------
Key: AMQ-2265
URL: https://issues.apache.org/activemq/browse/AMQ-2265
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.2.0
Environment: all
Reporter: Gary Tully
Assignee: Gary Tully
Fix For: 5.3.0
With a short time to live and a slow consumer, prefetched messages stored on the consumer expire. These get a delivery ack (so more mesages can be dispatched) but remain in the delivered list till a real ack is produced, on the consumption of an non expired message. With a large backlog and very slow consumer each prefetch set can be expired and the delivered list can grow to produce an ome.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-2265) potential OOM (OutOfMemory) on consumer
when all prefetched messages expire
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-2265.
-----------------------------
Resolution: Fixed
expired messages are no longer held in the deliveredMessages list on the consumer.
> potential OOM (OutOfMemory) on consumer when all prefetched messages expire
> ---------------------------------------------------------------------------
>
> Key: AMQ-2265
> URL: https://issues.apache.org/activemq/browse/AMQ-2265
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.2.0
> Environment: all
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.3.0
>
>
> With a short time to live and a slow consumer, prefetched messages stored on the consumer expire. These get a delivery ack (so more mesages can be dispatched) but remain in the delivered list till a real ack is produced, on the consumption of an non expired message. With a large backlog and very slow consumer each prefetch set can be expired and the delivered list can grow to produce an ome.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.