You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2009/03/10 11:16:50 UTC

[jira] Updated: (QPID-949) Implement Flow To Disk

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

Martin Ritchie updated QPID-949:
--------------------------------

    Status: Ready To Review  (was: In Progress)

> Implement Flow To Disk
> ----------------------
>
>                 Key: QPID-949
>                 URL: https://issues.apache.org/jira/browse/QPID-949
>             Project: Qpid
>          Issue Type: New Feature
>          Components: Java Broker
>    Affects Versions: M2.1
>            Reporter: Marnie McCormack
>            Assignee: Martin Ritchie
>             Fix For: M5
>
>
> Currently, the Java Broker can do one of two things with a message it has to deliver: 
> 1. Keep transient messages in memory until delivered
> 2. Write persistent messages to a message store (like BDB) and keep in memory until delivery complete
> This means that the broker is not able to avoid OoM exceptions i.e. send enough messages to the broker, especially if your consumers are not active, and you could bring the broker done once it explodes its available heap.
> RG to add more details and design proposal here please :-)

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


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org